Every wedding has one: the guest that takes it just a little too far. Whether it’s that one superfluous cocktail, the eyeliner application that’s a bit heavy-handed, or a hemline that’s just a few inches too short, weddings are ripe with potential pitfalls for guests.
To help you keep your beauty look appropriate, we enlisted the help of Makeup Artist Gabriel Almodovar, who offered his professional tips on wedding guest makeup done right.
The most important thing to remember is “the wedding is about the bride, not you!” Almodovar explains. For beauty, that means keep it soft, simple, and subdued. “As much as you might want to rock the gorgeous smoky eye or bright, bold lip, keep it understated as to not take away from the bride,” he says.
To enhance your features without overdoing it, “Focus on the skin first and foremost. BB Creams are perfect for weddings. They have just the right balance of coverage and softness,” Almodovar suggests. When considering bronzer, you should opt for a matte option that offers warmth without too much glimmer. We like Lancôme Star Bronzer.
The most appropriate complement to your fresh skin is subtle eye makeup. Almodovar suggests enhancing your brows, then layering “a light shimmery cream shadow from your lash line to brow. Maybelline Color Tattoo Metal 24hr Cream Gel Shadow in Barely Branded is great.”
Next, blend a soft taupe or greyish color on the lid into the crease (nothing too smoky!). Finally, “curl the lashes and apply two layers of black mascara.”
Put down the red lipstick, and finish your look by layering “a lip balm, lip pencil, and gloss that almost match your lip color,” Almodovar says. Two of our current neutral lipstick favorites are Bite Beauty Luminous Crème Lipstick in Muted Berry and Yves Saint Laurent Rouge Pur Couture in Blond Ingenu.
Ever been (or seen) that girl? Tell us your stories in the comments! Photos: Veer
About the Author:
Get our top stories straight to your inbox!
This email is already signed up!
Look out for our latest stories in your inbox.
Something went wrong. We're so sorry!