How is the intensity tuned for our product?<\/strong>\u00a0Levels author with the content in the Asset Creation Platform \u2014 your designers set the presentation range, and every user sees that range.<\/li>\n<\/ul>\n\n\n\nThe smoothing capability also earns its keep in export economics. Because region targeting and boundary handling run inside the normal render path, the full-resolution output needs no second pass \u2014 the clip a user shares is the clip they previewed, at the quality they previewed. Teams running upload pipelines value that predictability: no surprise reprocessing cost at export time, no quality gap between what was approved and what ships.<\/p>\n\n\n\n
Between the preview moment and the shared clip, smoothing is the capability users attribute the whole camera to. Getting it right per region, per frame, at authored intensity, is the foundation the rest of the beauty catalogue stands on.<\/p>\n\n\n\n
Two more notes from shipping teams. First, smoothing pairs naturally with the makeup layer: because they composite independently, a product can launch smoothing alone and add lipstick try-on a quarter later with no re-tuning of what shipped. Second, the smoothing preset catalogue is a product surface in its own right \u2014 teams that expose three named presets (natural day, polished evening, on-camera professional) see users settle on a favourite and stay, which is the behaviour every camera product wants more of.<\/p>\n\n\n\n
A final word on where smoothing sits in a launch plan: it is usually capability number one, shipped before reshaping and makeup, because it is the effect every user notices and no user has to be taught. The SDK’s modular arrangement supports exactly that sequencing \u2014 smoothing enables first, the rest of the stack joins when the roadmap calls for it, and every later capability inherits the same detection foundation the smoothing launch already validated. The first feature ships the stack; everything after it is content and modules.<\/p>\n\n\n\n
The launch checklist for smoothing is correspondingly short: enable the capability, apply your authored presets to the preview, verify the export matches, and read the first user sessions. Everything beyond that \u2014 regional tuning, seasonal presets, market-specific ranges \u2014 is catalogue work on a pipeline that already works, which is the pleasant kind of roadmap.<\/p>\n\n\n\n
Teams often note the same thing a month after shipping smoothing: the camera simply feels finished. That feeling is the product of a hundred per-frame decisions happening invisibly, and it is why region-targeted, boundary-preserving smoothing remains the anchor capability of the entire beauty family.<\/p>\n\n\n\n
FAQ<\/h2>\n\n\n\n
Does smoothing apply to recorded video as well as the live preview?<\/strong>
Yes. The same effect renders on capture, on the editor timeline, and on the live stream \u2014 one definition, three surfaces, consistent output.<\/p>\n\n\n\nWhat keeps the result looking natural rather than processed?<\/strong>
Two properties together: smoothing targets only the detected skin regions, and intensity presents through curated levels \u2014 both keep texture and detail where they belong.<\/p>\n\n\n\nCan users adjust smoothing themselves?<\/strong>
The presentation levels are authored per element \u2014 products typically expose light, standard, and strong, keeping user control inside a range the brand has approved.<\/p>\n\n\n\nHow does smoothing behave with multiple faces in frame?<\/strong>
Detection locates faces per frame and smoothing applies per detected region \u2014 the capability scales with the scene the camera sees.<\/p>\n\n\n\nDoes the smoothing preset update without an app release?<\/strong>
Yes. Presets are packages: a retuned look publishes through your own channel and reaches every platform at once.<\/p>\n","protected":false},"excerpt":{"rendered":"Skin smoothing in the Face Beauty SDK renders live on the camera preview: skin is refined as the frames arrive, while eyes, lips, brows, and the hairline keep their detail. The result is the natural retouch users expect from a modern camera app \u2014 visible immediately, applied to real skin regions rather than the whole […]<\/p>\n","protected":false},"author":1,"featured_media":542,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[40,46],"class_list":["post-541","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-face-ar-sdk","tag-face-ar-sdk","tag-face-beauty-sdk"],"_links":{"self":[{"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/posts\/541","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=541"}],"version-history":[{"count":1,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/posts\/541\/revisions"}],"predecessor-version":[{"id":543,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/posts\/541\/revisions\/543"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/media\/542"}],"wp:attachment":[{"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/media?parent=541"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/categories?post=541"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/tags?post=541"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"Real-Time](\"https:\/\/en.meishesdk.com\/blog\/wp-content\/uploads\/2026\/10\/2026102306551130.jpg\")
<\/a><\/figure>\n\n\n\n