{"id":532,"date":"2026-10-23T14:52:38","date_gmt":"2026-10-23T06:52:38","guid":{"rendered":"https:\/\/en.meishesdk.com\/blog\/?p=532"},"modified":"2026-10-23T14:52:39","modified_gmt":"2026-10-23T06:52:39","slug":"virtual-makeup-effects-in-the-face-beauty-sdk","status":"publish","type":"post","link":"https:\/\/en.meishesdk.com\/blog\/532.html","title":{"rendered":"Virtual Makeup Effects in the Face Beauty SDK"},"content":{"rendered":"\n

Virtual makeup in the Face Beauty SDK puts a full cosmetics counter inside your camera: lip colour, eye looks, and blush rendered live on the preview, placed precisely on the user’s facial features, and tracking the face as it moves. Users try a look in real time \u2014 no photo upload, no manual adjustment, no post-processing step.<\/p>\n\n\n\n

1. Product Positioning<\/h2>\n\n\n\n

Inside the Meishe Face Beauty SDK, virtual makeup rides the shared beauty stack: reshaping, smoothing, and makeup compositing from one detection pass per frame, real-time with no preprocessing stage. The stack runs on iOS, Android, Web, and Desktop (Windows), reaches smart hardware, and serves React Native and Flutter through the short-video solution. Virtual makeup is one of the compositing capabilities in that stack: elements are placed by facial landmarks, so lip colour follows the lips and eye looks follow the eyes through every head movement.<\/p>\n\n\n\n

2. What makeup does in your app<\/h2>\n\n\n\n
Makeup capability<\/th>What users see<\/th><\/tr><\/thead>
Lip colour<\/td>Chosen shade rendered on the lips, following the mouth through speech and movement<\/td><\/tr>
Eye looks<\/td>Eyeshadow and liner placed on the eye contour, matching each blink and turn<\/td><\/tr>
Blush and finishing elements<\/td>Colour placed on the cheeks, blended with the live image<\/td><\/tr>
Per-element intensity<\/td>Light, standard, or strong presentation for each element \u2014 a curated range, not one fixed value<\/td><\/tr>
Complete looks<\/td>Pre-combined element sets users apply with one tap<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Every element shares the same per-frame landmark data that drives smoothing and reshaping, so the whole beauty stack \u2014 including makeup \u2014 runs from one detection pass.<\/p>\n\n\n\n

\"Virtual<\/a><\/figure>\n\n\n\n

3. How the placement stays accurate<\/h2>\n\n\n\n

The precision behind a convincing makeup effect comes from landmark analysis. The SDK places reference points on the facial structure each frame \u2014 the contour, the eyes, the brows, the lips, the nose \u2014 and positions each makeup element against those points. That is why lip colour sits on the lips and moves with the mouth, rather than floating as a static overlay.<\/p>\n\n\n\n

Two practical consequences follow:<\/p>\n\n\n\n

    \n
  • Makeup is a compositing layer above smoothing and reshaping<\/strong>, so changing a lip shade never forces re-processing of the skin work \u2014 the layers are independent.<\/li>\n\n\n\n
  • The same element renders consistently everywhere.<\/strong>\u00a0Because placement is computed per frame from landmarks, the element looks right at any head angle the detection supports, on camera and on the exported clip alike.<\/li>\n<\/ul>\n\n\n\n
    \n

    The snippet below is schematic. Names and signatures are illustrative, not the shipped API.<\/p>\n<\/blockquote>\n\n\n\n

    \/\/ Illustrative: applying a complete look and tuning one element.\nimport { createBeautyRuntime } from \"@meishe\/beauty\"; \/\/ placeholder name\n\nconst rt = await createBeautyRuntime({ platform: \"ios\" });\n\nawait rt.looks.apply(\"look.evening.01\");              \/\/ complete look, one tap\nawait rt.elements.setLevel(\"lip.satin.maple\", \"light\"); \/\/ per-element intensity<\/code><\/pre>\n\n\n\n
    4. What this gives a product team<\/h2>\n\n\n\n
      \n
    • A try-on experience without friction.<\/strong>\u00a0Users see the shade on their own face in the live preview \u2014 the fastest path from browsing to deciding.<\/li>\n\n\n\n
    • Content that ships at campaign speed.<\/strong>\u00a0Makeup elements are data packages: a new seasonal collection publishes through your channel with no app release.<\/li>\n\n\n\n
    • One integration for the whole beauty stack.<\/strong>\u00a0Makeup rides the same detection pass as smoothing and reshaping, so enabling it costs no second analysis and no second integration.<\/li>\n<\/ul>\n\n\n\n
      5. Why teams choose Meishe<\/h2>\n\n\n\n
      Advantage<\/th>What it means for your project<\/th><\/tr><\/thead>
      Self-developed engine<\/td>The cross-platform audio\/video processing engine used across the product family, refined through years of shipping<\/td><\/tr>
      Real-time, no preprocessing<\/td>Makeup renders the moment the camera opens<\/td><\/tr>
      One detection pass<\/td>Smoothing, reshaping, and makeup all run from the same per-frame analysis<\/td><\/tr>
      Per-element intensity<\/td>Each element presents at light, standard, or strong \u2014 tuned ranges, not sliders<\/td><\/tr>
      Content pipeline included<\/td>Makeup collections author in the Asset Creation Platform and publish as packages<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      6. What shipping teams ask first<\/h2>\n\n\n\n
        \n
      • Can makeup run together with smoothing and reshaping?<\/strong>\u00a0Yes \u2014 all three are layers of the same stack, sharing one detection pass per frame.<\/li>\n\n\n\n
      • How do seasonal collections reach users?<\/strong>\u00a0As package publishes through your own delivery channel; the app binary stays untouched.<\/li>\n\n\n\n
      • Who creates the elements?<\/strong>\u00a0Your designers in the Asset Creation Platform, or Meishe’s Special Effects Customization service for produced collections.<\/li>\n<\/ul>\n\n\n\n
        The try-on surface also compounds with the rest of the beauty stack. A user can wear smoothing, reshaping, and a complete makeup look together \u2014 one detection pass, three capabilities, one live preview. Product teams use that combination to define signature styles for their app: a natural everyday default, a stronger evening preset, both delivered by the same runtime with no additional integration work.<\/p>\n\n\n\n
        After launch, the catalogue becomes the growth lever. Each new collection is a content decision \u2014 authored, reviewed, published \u2014 and the try-on experience users loved on day one keeps refreshing itself without the app ever visiting a store review queue.<\/p>\n\n\n\n
        For commerce products, the same runtime closes a measurable gap: the difference between browsing a shade swatch and seeing it on your own face. The live preview answers the question a product page cannot, and the try-on session becomes the highest-intent moment in the funnel \u2014 with the share and save actions your team attaches to it.<\/p>\n\n\n\n
        A note on what the SDK expects from your app: the camera surface, the permission flow, and the catalogue UI are yours. That boundary is deliberate \u2014 products differ in how they present a cosmetics counter, and the SDK concentrates on what makes try-on convincing in the first place: placement, tracking, and real-time rendering. Your team wraps it in the brand experience your users already know.<\/p>\n\n\n\n
        Integration effort reflects the same focus.<\/strong> The makeup layer joins a beauty stack your app may already run; if smoothing is integrated, makeup arrives as packages on the same runtime rather than as a second integration project. And if try-on is your first Meishe capability, the same stack grows into reshaping, smoothing, and the wider effects family as the roadmap expands.<\/p>\n\n\n\n
        Run together, those properties make the makeup capability a safe bet for the product roadmap: small to add, cheap to grow, and immediately visible to users on the very first preview frame.<\/p>\n\n\n\n
        FAQ<\/h2>\n\n\n\n
        Does the makeup hold up during video calls and live streaming?<\/strong>
        Yes. Placement recomputes every frame from landmarks, so the look tracks the face through movement in any live surface.<\/p>\n\n\n\n
        Can users adjust how strong an effect is?<\/strong>
        Yes \u2014 per-element intensity presents each element at light, standard, or strong, keeping results inside a curated range your team controls.<\/p>\n\n\n\n
        Is makeup available on all platforms?<\/strong>
        The Face Beauty SDK covers iOS, Android, Web, Desktop (Windows), and smart hardware, with React Native and Flutter through the short-video solution \u2014 makeup is part of the stack everywhere it runs.<\/p>\n\n\n\n
        Can we ship our own lipstick collection?<\/strong>
        Yes. Elements and looks are packages: your collection authors in the Asset Creation Platform and publishes through your channel like any other content.<\/p>\n\n\n\n
        Does trying a shade require a photo upload?<\/strong>
        No \u2014 everything renders live on the camera preview. That immediacy is what makes virtual try-on convert.<\/p>\n","protected":false},"excerpt":{"rendered":"
        Virtual makeup in the Face Beauty SDK puts a full cosmetics counter inside your camera: lip colour, eye looks, and blush rendered live on the preview, placed precisely on the user’s facial features, and tracking the face as it moves. Users try a look in real time \u2014 no photo upload, no manual adjustment, no […]<\/p>\n","protected":false},"author":1,"featured_media":533,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[271,40,46,403],"class_list":["post-532","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-face-ar-sdk","tag-effects","tag-face-ar-sdk","tag-face-beauty-sdk","tag-makeup"],"_links":{"self":[{"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/posts\/532","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/comments?post=532"}],"version-history":[{"count":1,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/posts\/532\/revisions"}],"predecessor-version":[{"id":534,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/posts\/532\/revisions\/534"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/media\/533"}],"wp:attachment":[{"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/media?parent=532"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/categories?post=532"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/tags?post=532"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}