Beauty has been one of the strongest commercial proving grounds for augmented reality. Shoppers who can see a lipstick, foundation, or eyeshadow on their own face buy more, return less, and stay engaged longer. The global virtual makeup try-on market was valued at USD 1.11 billion in 2024 and is projected to grow from USD 1.28 billion in 2025 to USD 1.86 billion by 2032.
The product surface has widened, too. AR beauty now lives inside e-commerce stores, smart mirrors, video calls, livestreaming apps, photo editors, dating apps, and karaoke products. Each of those uses the same building blocks: face tracking, segmentation, real-time rendering, and a tuned set of shaders for skin, lips, hair, and eyes.
The catch is that those building blocks are hard. Real-time computer vision on mobile has tight constraints, and beauty rendering has to look believable next to physical products. Most product teams are not staffed to build all of it. That is why Beauty AR SDKs like Banuba have become the default choice for shipping AR beauty in 2027.
AR beauty features rely on real-time face tracking, neural networks for skin and lip segmentation, GPU-accelerated rendering, and color-accurate shaders that simulate how cosmetics interact with light and skin. Building all of that in-house can take six to twelve months of specialist engineering work. A beauty AR SDK like Banuba packages tracking, segmentation, makeup APIs, and rendering into a single integration, which lets product teams ship working features in weeks rather than years.
Stay tunedKeep up with product updates, market news and new blog releases
[navigation]
TL;DR
AR beauty drives real commerce results: the global virtual try-on market was worth USD 9.2 billion in 2023, is estimated at USD 18.1 billion for 2026, and is projected to reach USD 46.4 billion by 2030 at a 26.4% CAGR, with beauty one of the fastest-moving verticals.
Building from scratch means owning face tracking, segmentation models, GPU shaders, and a multi-platform rendering pipeline. That is rarely the right use of a product team's runway.
Banuba's Beauty AR SDK unites those layers into a single integration, with tested support for iOS, Android, Web, Windows, macOS, Unity, Flutter, and React Native.
SDKs make sense when speed to market matters, when AR is a feature within a larger product, or when the team lacks a dedicated computer vision group.
Banuba's Beauty AR SDK ships makeup, beautification, skin retouch, and color analysis features. Looké, a niche beauty brand in Indonesia, built its virtual makeup app on it and passed 55,000 installs.
Why Beauty AR Features Succeed in Apps
Three Banuba-powered products show how the same underlying capability translates into very different commercial outcomes. Boca Rosa, an influencer-led Brazilian cosmetics brand, used Banuba's TINT virtual try-on at a pre-launch event and recorded more than 1.7 million try-on sessions and roughly $900,000 in sales in 4 hours. Looké, an Indonesian niche brand, built a full virtual makeup app on Banuba's beauty AR SDK and crossed 55,000 installs with mostly 5-star reviews. FaceYoga by Mental Growth used Banuba's Face AR SDK to power a "before and after" wellness feature and reached 20,000+ downloads.
None of those teams invented the technology. They all relied on the same primitives. What separates a strong AR beauty feature from a forgettable one is consistent across all three:
Real-time response. Anything above roughly 100 ms of latency between head movement and overlay update breaks the illusion.
Lifelike color. Lipstick has to read as matte or glossy. Foundation has to blend with skin tone, not paint over it. Highlighter has to react to light.
Stable tracking under real conditions. People move, tilt their heads, hold their phones at strange angles, and use bad lighting.
A clear next action. The AR layer is rarely the goal. The goal is buying, sharing, calling, or streaming. The AR has to get out of its own way.
What AR Beauty Features Have to Do
Most "core capabilities" lists for AR beauty are flat checklists. That hides where the real work lives. A more useful way to think about it is to follow what happens between the moment a user opens the camera and the moment a virtual lipstick lands on their lip. Each step in that chain has its own engineering cost, and each step is something a team will either build or inherit from an SDK.
Step 1. The camera frame arrives. The first job is to identify the face within the frame and determine whether it is one face, several faces, or no face at all. This is the detection layer. It has to run on every frame on devices ranging from a recent iPhone to a $150 Android, without dropping below interactive frame rates.
Step 2. The face is tracked, not just detected. Detection alone is not enough. The system has to know how the face is oriented in 3D space, where the lips and eyes are, how the head is rotating, and whether the user is partially occluded by hands, glasses, or hair.
Step 3. Skin, lips, and hair are separated from everything else. A lipstick has to apply to lips, not to the area around them. A hair color has to apply to hair, not to a shirt collar. This is segmentation, and it is where neural networks earn their keep. Each surface (skin, lips, hair, eyes, teeth, neck) needs its own trained model.
Step 4. The cosmetic is rendered with realistic light behavior. This is the part most in-house builds underestimate. A matte lipstick should look matte. A satin lipstick should pick up a soft highlight. A foundation should respect the underlying skin tone instead of painting over it. A highlighter should react when the user turns toward a light source. This requires shader work that goes well beyond a color overlay, and it must be tuned for each finish type.
Step 5. Beautification effects run alongside, not instead. Skin smoothing, acne removal, eye bag reduction, teeth whitening, and face morphing are usually applied at the same time as makeup.
Step 6. Output goes to wherever the product needs it. Sometimes, that is a live preview on the user's screen. Sometimes it is a recorded video for a social post. Sometimes it is a photo for an e-commerce review. Sometimes it is a video call frame routed through an Agora Extension, Zoom, or a custom WebRTC stack. The integration layer has to plug into all of those without rewriting the rendering pipeline each time.
Step 7. The whole chain runs in real time on the user's device. This is the constraint that ties everything together. AR beauty cannot send a video to a server and wait for a response. It has to run locally, fast enough that head movement does not lag, and on a thermal and battery budget the user will tolerate.
A team that builds AR beauty in-house signs up for every step in that chain. A team that adopts an SDK signs up for steps 1, 2, 3, 4, and 5 to be solved already, and spends its engineering effort on steps 6 and 7 in the context of its specific product.
In-house Build vs. Integrating a Beauty AR SDK
Building In-house
Building AR beauty internally is technically possible. Several teams do it, usually because they have specific IP requirements or a dedicated computer vision group. The realistic shape of that project looks like this.
Tech stack and components
Native frameworks (Swift/Metal on iOS, Kotlin/OpenGL ES or Vulkan on Android)
Cross-platform layers (Flutter, React Native, or Unity if multi-platform support is required)
A face tracking model trained on a balanced dataset across skin tones, ages, and lighting conditions
Segmentation models for skin, lips, and hair
A custom GPU shader library for cosmetics and skin retouch
A LUT and color management system
An asset pipeline for digitizing cosmetic products
A device compatibility matrix and a thermal/battery testing harness
Risks
Computer vision research time. Tracking on mobile under poor lighting and occlusion is a hard problem, and getting it stable usually takes multiple iterations.
Performance regressions on mid-range and low-end Android devices. AR beauty has to work on phones that cost $150, not just flagships.
Color accuracy on diverse skin tones. Models trained on narrow datasets fail in production. Building a balanced dataset is expensive.
Maintenance cost. Every iOS or Android release can break camera and GPU behavior. New device form factors arrive every quarter.
Time to market. Six to twelve months is a typical floor before an in-house beauty AR feature is production-ready, and that is before any commercial use cases are added on top.
Integrating a Beauty AR SDK
The SDK option trades a recurring license cost for a much shorter critical path. The team integrates a tested binary with a documented API, plugs it into the existing product, and spends engineering time on the parts that are actually unique to the business: UX, commerce flow, asset library, brand customization.
What a beauty AR SDK gives a team
Pre-built face tracking that has already been validated across thousands of devices
Pre-trained neural networks for skin, lip, and hair segmentation
Pre-built shaders and effect libraries for makeup, hair color, and skin retouch
Cross-platform parity, so iOS, Android, and Web behave the same
A documented integration flow with code samples and platform plugins
A vendor team that maintains the underlying tech as devices and OSes change
Tradeoffs
License cost replaces internal headcount cost. For most teams, the math favors the SDK, but it should still be modeled.
Customization happens through the SDK's effect editor and API, not by editing model weights.
Some highly specific use cases may need vendor R&D collaboration.
The honest version of the tradeoff is that an SDK hands the team the tracking, segmentation, and rendering layers already built and maintained, and leaves the product-specific work in the team's hands. The remaining customization is done through the SDK's tools.
In-house vs. Beauty AR SDK Compared
What you decide
Build in-house
Banuba Beauty AR SDK
Face tracking
Train and tune your own model across skin tones, angles and lighting
68 facial anchor points on a 3D mesh of up to 3,308 vertices, maintained by Banuba
Segmentation
One trained model per surface: skin, lips, hair, eyes, teeth, neck
Pre-trained models ship with the SDK
Makeup rendering
Build a shader library per finish (matte, satin, glossy, shimmer)
Eyeshadow, eyeliner, lashes, blusher, highlighter, contour and lipstick across four finishes
Beautification
Separate neural networks for acne, eye bags, neck, teeth
Included: smoothing, skin tone, morphing, teeth whitening, acne removal, eye bag and neck smoothing, LUT color correction
Platforms
A separate implementation and test matrix per platform
One integration for iOS, Android, Web, Windows, macOS, Unity, Flutter and React Native
Device floor
You define and test it yourself
iOS 13+, Android 8.0+ (API 26+), browsers with WebAssembly
Effect authoring
Custom tooling or hand-written shaders
Banuba Studio, a web editor; existing 3D assets can be imported
Time to first working feature
Six to twelve months of specialist work
One to four weeks of integration, depending on platforms and UI depth
Maintenance
Your team re-tests on every OS and device release
Banuba maintains the tracking, models and platform plugins
Cost shape
Internal headcount
A custom licence quote, built from the platforms you ship on, the feature categories you turn on and your monthly active users; billed yearly, and a 14-day free trial covers every feature first
SDK-focused Implementation: Banuba Beauty AR SDK
Banuba's Beauty AR SDK packages real-time face beautification and virtual makeup try-on into a single integration. It runs on iOS, Android, Web, macOS, Windows, Unity, Flutter, and React Native, and replaces the parts of an AR beauty stack that most teams should not be building themselves: face tracking, segmentation models, makeup rendering, and beautification effects.
The capability set covers both sides of AR beauty:
Makeup
Eyeshadow with adjustable color and transparency
Eyeliner for upper or lower eyelid
Eyelashes of any length and color
Blusher on upper cheeks
Highlighter on nose, forehead, and chin
Contour on lower cheeks and upper forehead
Lipstick across matte, satin, glossy, and shimmer finishes
Beautification
Skin smoothing and wrinkle softening
Skin tone enhancement
Face morphing for cheeks and nose
Teeth whitening
Expressive eyes effect
Acne removal driven by a feature recognition neural network
Eye bag and neck smoothing through dedicated neural networks
Color correction via LUTs
The SDK is built on Banuba's Face Tracking Software, which uses a 3D face model rather than a flat landmark map. The tracker tracks 68 facial anchor points on the visible face mesh and runs alongside Banuba's patented anti-jitter mechanism for smooth, stable overlays. The face tracker holds the lock across the full -80° to +80° head-angle range, supports 360 degrees of device rotation, works in low-light environments, and handles up to 70% facial occlusion.
Recent releases push the SDK further into AI-driven personalization. Banuba's automated seasonal color analysis feature categorizes individuals into seasonal color palettes based on the tone of their skin, hair, and eyes, helping users identify which shades enhance their natural features. In December 2025, Banuba announced upgrades to its Face AR SDK, introducing improvements to the virtual background feature and launching a new face shape detection capability, both of which feed directly into the personalization logic that beauty apps rely on.
The commercial track record is concrete. Companies that added Banuba try-on have reported higher add-to-cart rates, higher sales, and lower return rates. Océane, a Brazilian cosmetics manufacturer and retailer, moved its add-to-cart rate from an industry-average 3% to 20.15% in the first month of its TINT pilot, and later set a new peak at 32%.
Integration overview
At a conceptual level, integrating the Beauty AR SDK into a product looks like this:
Get a license and client token. A 14-day free trial covers every feature on every supported platform.
Add the SDK to the build. iOS via CocoaPods or SPM, Android via Maven, Web via the @banuba/webar npm package, Flutter via the banuba_sdk pub package, React Native via the @banuba/react-native npm package, or Unity via the Unity plugin.
Initialize the SDK with the client token and connect it to the camera input or video stream.
Call the relevant API.
Customize. Banuba Studio is a web-based editor for building effects compatible with the SDK. Existing 3D assets can be imported and adapted.
Ship. The SDK ensures cross-platform parity, so the same effects render consistently on iOS, Android, and the Web.
Full implementation guides, platform-specific requirements, and code samples live in the official documentation:
When teams ask whether to build or buy AR beauty, the answer usually falls into three categories.
Is AR beauty the product, or a feature inside the product? If it is a feature, an SDK is almost always the right call. The product team's time is better spent on the surrounding experience.
Does the team have an in-house computer vision and GPU shader group? If not, the SDK route avoids the multi-quarter ramp required to hire and ship that capability.
Does the use case need IP-differentiated tracking or rendering? If yes (and this is rare outside of vendors selling AR tech itself), a custom build may be justified. If no, an SDK is faster and lower-risk.
For beauty brands, e-commerce platforms, video and streaming apps, social and dating products, and wellness apps, the answer is consistently the same: use an SDK and spend the engineering budget on the parts of the product that customers actually pay for.
Conclusion
AR beauty has matured from a marketing experiment into a measurable layer for commerce and engagement. The technical requirements (real-time tracking, multi-class segmentation, accurate shading across skin tones, cross-platform parity) are the same regardless of whether the use case is virtual makeup try-on, video call beautification, or a wellness "before and after" experience. Most product teams should not be building all of that themselves.
A beauty AR SDK collapses six to twelve months of specialist engineering into a few weeks of integration work, and shifts maintenance onto a vendor whose full-time job is keeping the underlying technology current.
If AR beauty is on the roadmap, the practical next step is to start a 14-day free trial, integrate the SDK into a prototype, and measure against the team's existing baseline.
No. A mobile or web developer comfortable with the platform's standard tooling can integrate Banuba's Beauty AR SDK using the documented samples. The deep computer vision work (face tracking, segmentation, shaders) is handled inside the SDK. Custom effects can be built in Banuba Studio without engineering.
Banuba Beauty AR SDK supports iOS (13.0+), Android (8.0+, API level 26+), Web (browsers with WebAssembly), macOS, Windows, and Unity. Cross-platform plugins are available for Flutter and React Native, with shared rendering behavior across platforms.
A working prototype typically takes one to four weeks, depending on the number of platforms and the depth of UI and asset work. Looké built and shipped a full virtual makeup app on Banuba in a few weeks, compared with the months or years a full in-house build would have required. The 14-day free trial covers the whole SDK, and Banuba Face AR SDK pricing is a custom quote built from the platforms you ship on, the feature categories you turn on, and your monthly active users, so a team can benchmark first and scope the license afterward.