AI Virtual Makeup Try-On: From Prototype to Production

We design and deploy artificial intelligence systems: from prototype to production-ready solutions. Our team combines expertise in machine learning, data engineering and MLOps to make AI work not in the lab, but in real business.
Showing 1 of 1All 1564 services
AI Virtual Makeup Try-On: From Prototype to Production
Complex
~1-2 weeks
Frequently Asked Questions

AI Development Areas

AI Solution Development Stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1360
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1251
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    957
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1188
  • image_logo-advance_0.webp
    B2B Advance company logo design
    646
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    929

AI Virtual Makeup Try-On

Beauty brands face a dilemma: how to let customers try on cosmetics without physical contact? Naive 2D image overlays look unnatural—they ignore reflections, skin texture, and facial expressions. We solve this with a hybrid architecture: landmark-based detection for real-time and AI generative models for high-quality photos. Our experience in Computer Vision (5+ years, 20+ projects in the beauty segment) shows that this approach reduces cosmetic returns by 30% thanks to more accurate shade matching. As a result, clients get not just a try-on tool, but one that increases cart conversion by 25% and cuts return rates.

For real-time scenes, we use MediaPipe Face Mesh [^1]—a solution from Google that detects 468 facial keypoints with under 5 ms latency. For high-quality photos, we apply Stable Diffusion Inpainting with a mask of application zones.

Comparing Approaches: Landmark-Based vs AI-Generative

Characteristic Landmark-Based (MediaPipe) AI-Generative (Stable Diffusion)
Speed < 5 ms (real-time) 5–15 sec (offline)
Overlay accuracy High on contours High on texture
GPU requirements None (WebGL in browser) Yes (GPU class T4+)
Realism Medium (smoothed) High (accounts for lighting)
Application scope Live streams, AR filters Photo try-on in app

Why Hybrid Approach is More Effective Than Pure AI?

For real-time scenes, latency is critical: MediaPipe offers a 100x speed advantage over generative models. At the same time, positioning accuracy for lips, eyelids, and cheekbones is high enough that jagged edges can be smoothed with bilinear filtering. We guarantee a stable 30 FPS frame rate even on mid-range mobile devices. For photos, where quality trumps speed, we use Stable Diffusion XL Inpainting with prior face segmentation—the model receives a mask of application zones and generates texture accounting for skin relief and incident light. This produces a living makeup effect, not a flat overlay. Processing time is 5–15 seconds per image, acceptable for user photos in an app.

How We Ensure Real-Time at 30 FPS?

Key is using WebGL for rendering and an optimized WASM build of MediaPipe. We avoid CPU-GPU data copying by directly accessing textures via WebGL2. As a result, on a mid-range smartphone (Snapdragon 865+) we get stable 30 FPS with under 5 ms latency. Additionally, we apply bilinear filtering for edge smoothing and adaptive bitrate for the video stream.

MediaPipe Approach (Real-Time)

import mediapipe as mp
import cv2
import numpy as np
from PIL import Image

class RealTimeMakeupAR:
    def __init__(self):
        self.face_mesh = mp.solutions.face_mesh.FaceMesh(
            static_image_mode=False,
            max_num_faces=1,
            min_detection_confidence=0.5,
            min_tracking_confidence=0.5
        )

    LIPS_INDICES = [61, 185, 40, 39, 37, 0, 267, 269, 270, 409, 291, 375, 321, 405, 314, 17, 84, 181, 91, 146]
    UPPER_LID_L = [362, 382, 381, 380, 374, 373, 390, 249, 263, 466, 388, 387, 386, 385, 384, 398]
    CHEEKS_L = [36, 31, 228, 229, 230, 231, 232, 233, 244, 245, 188, 174, 177, 215, 213, 192]

    def apply_lipstick(self, frame, color, opacity=0.6):
        rgb = cv2.cvtColor(frame, cv2.COLOR_BGR2RGB)
        results = self.face_mesh.process(rgb)
        if not results.multi_face_landmarks:
            return frame
        landmarks = results.multi_face_landmarks[0]
        h, w = frame.shape[:2]
        lip_points = np.array([
            [int(landmarks.landmark[i].x * w),
             int(landmarks.landmark[i].y * h)]
            for i in self.LIPS_INDICES
        ], dtype=np.int32)
        overlay = frame.copy()
        cv2.fillPoly(overlay, [lip_points], color[::-1])
        return cv2.addWeighted(frame, 1 - opacity, overlay, opacity, 0)

How AI Generative Try-On Works?

For photos, where quality matters more than speed, we use Stable Diffusion XL Inpainting with prior face segmentation. The model receives a mask of application zones (lips, eyelids, cheekbones) and generates texture accounting for skin relief and incident light. This produces a living makeup effect, not a flat overlay. Processing time is 5–15 seconds per image, acceptable for user photos in an app.

AI Generative Approach (High Quality)

from diffusers import StableDiffusionXLInpaintPipeline
import torch
from PIL import Image
import io

class AIPhotoMakeupTryOn:
    def __init__(self):
        self.pipe = StableDiffusionXLInpaintPipeline.from_pretrained(
            "diffusers/stable-diffusion-xl-1.0-inpainting-0.1",
            torch_dtype=torch.float16
        ).to("cuda")
        self.face_parser = FaceParser()

    def apply_makeup_ai(self, photo, makeup_style, intensity=0.7):
        img = Image.open(io.BytesIO(photo)).convert("RGB")
        face_mask = self.face_parser.get_makeup_zone_mask(img)
        result = self.pipe(
            prompt=f"beautiful makeup, {makeup_style}, natural skin texture",
            negative_prompt="unnatural, heavy, clown, overdone",
            image=img,
            mask_image=face_mask,
            strength=intensity,
            num_inference_steps=30,
            guidance_scale=8.0
        ).images[0]
        buf = io.BytesIO()
        result.save(buf, format="PNG")
        return buf.getvalue()
Pipeline Tuning Details To boost realism, we fine-tune the model on a dataset of 5000 professional beauty photos with diverse skin tones and lighting. We use LoRA adapters, which speeds up training and reduces model size. Inference runs on GPU class T4 using TensorRT for latency optimization.

Development Stages of Virtual Try-On

Stage Duration Result
Requirements analysis and reference gathering 3–5 days Technical specification, interface prototypes
Architecture selection and model preparation 5–7 days Choice of landmark-based or AI generative approach
Detection and rendering implementation 7–10 days Working prototype in browser or app
Integration with product catalog 3–5 days API connection, shade synchronization
Testing and optimization 5–7 days Device testing, performance tuning
Deployment and documentation 2–4 days Rollout, team training

What is Included in the Work

Our certified experience in Computer Vision allows us to deliver turnkey projects. As a result, you receive:

  • documentation: architecture diagram, API description, integration guide
  • source code with comments and CI/CD pipeline
  • team training on system operation
  • support during industrial operation (SLA of at least 99.9%)

Product Architecture

Web/Mobile App
├── Camera/Photo mode
│   ├── Real-time: MediaPipe WASM + WebGL (< 5ms)
│   └── Photo: AI inpainting API (10–15 sec)
├── Product catalog (lipstick, eyeshadow shades)
├── Shade picker + color mixer
└── Share / Download result

Timelines: browser real-time AR makeup (MediaPipe) — 3–4 weeks. AI photo try-on API — 1–2 weeks. Full mobile app with catalog — 3–4 months.

Browser Real-Time Implementation

import * as faceMesh from '@mediapipe/face_mesh';
import * as drawingUtils from '@mediapipe/drawing_utils';

const faceMeshInstance = new faceMesh.FaceMesh({locateFile: (file) => {
    return `https://cdn.jsdelivr.net/npm/@mediapipe/face_mesh/${file}`;
}});

faceMeshInstance.setOptions({
    maxNumFaces: 1,
    minDetectionConfidence: 0.5,
    minTrackingConfidence: 0.5
});

function renderLipstick(ctx, landmarks, color, opacity) {
    const lipIndices = [61, 185, 40, 39, 37, 0, 267, 269, 270, 409, 291, 375];
    ctx.globalAlpha = opacity;
    ctx.fillStyle = color;
    ctx.beginPath();
    lipIndices.forEach((idx, i) => {
        const lm = landmarks[idx];
        if (i === 0) ctx.moveTo(lm.x * canvas.width, lm.y * canvas.height);
        else ctx.lineTo(lm.x * canvas.width, lm.y * canvas.height);
    });
    ctx.closePath();
    ctx.fill();
    ctx.globalAlpha = 1.0;
}

Contact us for a pilot project — get a demo within 5 days. Request a consultation — we'll select the optimal architecture for your tasks.

[^1]: MediaPipe Face Mesh — library for detecting and tracking facial keypoints.

Generative AI Development: From Prompt to Production API

We often receive a task "generate a product image" — on the surface it seems simple. But behind this lies a choice between dozens of models, configuring the inference pipeline, manually solving consistency issues, integrating into the product backend, and answering why the model generates hands with six fingers in staging but not in production. Let's break down the directions we work with.

Image Generation: From Prompt to Production API

The current landscape includes FLUX.1 [dev/schnell/pro] from Black Forest Labs and Stable Diffusion 3.5. FLUX.1 [schnell] takes 4 steps instead of 20–50 for SDXL — 5–12 times faster — while maintaining higher quality. On an A100 80GB — 1.2–1.8 s per 1024×1024 image at batch_size=4.

A typical deployment issue: FLUX.1 [dev] requires 24+ GB VRAM in fp16. On A10G 24GB it fits tightly; at batch_size>1 — OOM. Solution: torch_dtype=torch.bfloat16 + enable_model_cpu_offload() from diffusers, or quantization via bitsandbytes to NF4 — minimal quality drop, memory consumption drops to 12–14 GB.

ControlNet and IP-Adapter are key tools for production tasks where controllability is needed. ControlNet with Canny/Depth/Pose maps provides structural control. IP-Adapter (especially IP-Adapter-FaceID) allows transferring character identity to generations — this is the foundation for personalized content. More about ControlNet can be found on Wikipedia.

Case study: e-commerce photography. A retailer with 8000 SKUs needed lifestyle photos for each product. Pipeline: product segmentation (Segment Anything Model 2) → background removal → inpainting with FLUX.1 [dev] using product image as IP-Adapter reference → upscale via RealESRGAN_x4plus. The generation cost is negligible compared to professional photography, providing huge savings. Throughput — 200 images/hour on 2× A100. Our extensive experience from 30+ projects ensures we select the optimal model for your task — an evaluation can be obtained upfront.

Why Is Model Selection Only Half the Battle?

Fine-tuning for a Specific Style or Character

Dreambooth and LoRA are the standard for adapting to a specific visual style or object. LoRA trains in 2–4 hours on 20–30 reference images on a single A100. Rank 16–32 is usually sufficient for style; rank 64+ is needed for precise face reproduction.

A common mistake: training LoRA too long — the model overfits to references, losing the ability to vary. Sign: at cfg_scale=7, all images look like copy-paste of references. Solved by early stopping (usually 1500–2000 steps for 20 images) and prior_preservation_loss.

For deeper customization — full fine-tuning via diffusers + accelerate with FSDP on multiple GPUs. But that already takes 40–80 hours of training and requires a truly large dataset (1000+ images).

Comparison of Image Generation Approaches

Model Speed (1024×1024, A100) Quality (CLIP score) Controllability (ControlNet, IP-Adapter) VRAM (fp16)
Stable Diffusion 3.5 2.0–3.5 s 0.28–0.31 via ControlNet (allowed) 16–20 GB
FLUX.1 [schnell] 0.8–1.2 s 0.30–0.33 limited (no ControlNet) 12–14 GB (4‑step)
FLUX.1 [dev] 3–5 s (50 steps) 0.32–0.34 via IP-Adapter, ControlNet (adapter) 24+ GB
Midjourney (API) 5–10 s (queue) 0.31–0.33 prompt + style reference not required

Video Generation: Which Models Are Best?

Model Availability Duration Resolution Controllability
Sora (OpenAI) API (limited) up to 60 s 1080p prompt, image-to-video
Wan2.1 (Alibaba) open weights up to 81 frames 720p prompt, I2V, V2V
CogVideoX-5B open weights 6 s 720p prompt, I2V
Kling 1.6 API up to 30 s 1080p prompt, I2V
Mochi-1 open weights 5.4 s 480p prompt

Open-weight video models still lag behind commercial ones in stability and length. Wan2.1 is the best choice for self-hosting: 14B parameters, runs on 2× A100, delivers acceptable quality for short clips.

The main pain of video generation is temporal consistency: the character changes clothing color at the third second, objects "drift." Partial solution — generation with motion_bucket_id and noise_aug_strength in Stable Video Diffusion, or using I2V (image-to-video) instead of pure text-to-video. As noted in VideoPoet research, consistency is achieved by training on long sequences.

AnimateDiff remains a working tool for short loops and motion effects on top of SD/FLUX. Not Sora, but deployable locally and predictable.

Music and Audio Generation

AudioCraft from Meta (MusicGen + AudioGen) is a production-ready stack for music generation. musicgen-large (3.3B) generates 30 s of music in ~8 s on A100. Control via text prompt and melody conditioning — you can specify a melody by humming.

Stable Audio Open from Stability AI is an alternative with length up to 47 s, better structural control (intro/verse/chorus). Deployment is similar: diffusers + FastAPI.

For voice-over and dubbing — ElevenLabs API or self-hosted XTTS v2 (see Speech AI service). For sound design and foley — AudioGen.

3D Generation: Current Practical State

3D generation has not yet reached the same maturity as 2D. But for specific tasks, tools are already working:

TripoSG and Shap-E — text/image-to-3D. Shap-E from OpenAI generates simple 3D meshes in seconds, but geometry is rough. TripoSG gives more detailed results but requires post-processing (remeshing, UV unwrapping).

Wonder3D and Zero123++ — 3D reconstruction from a single image. They work by generating multi-views (6–8 views) and then 3D reconstruction via NeuS or instant-ngp.

Gaussian Splatting (3DGS) — not generation, but reconstruction from a series of photos/videos. For product cards and real estate it's already production: 50–200 photos → 3DGS model in 15–30 min on RTX 4090 → interactive 3D viewer in browser.

What Infrastructure Is Needed for Generative AI Deployment?

Critical for generative models:

  • Task queue — Celery + Redis or Ray Serve. Synchronous HTTP for image generation is unacceptable with >5 concurrent requests.
  • Caching — similar prompts yield similar results. Semantic cache via embeddings (faiss + sentence-transformers) can reduce GPU load by 20–40%.
  • Quality monitoring — CLIP score for text-image alignment, FID for evaluating generation distribution. Integrate into MLflow or Weights & Biases.
  • Storage — generated images immediately to S3/MinIO, not on the inference server disk.

What's Included in the Deliverables

We take the project turnkey — from model selection to deployment and monitoring. The result includes:

  • Model (or API integration) with performance benchmarks (latency p99, throughput).
  • Pipeline documentation (prompt engineering guide, model card, dependency versions).
  • Integration with your backend (REST/gRPC, queues).
  • Configured monitoring (dashboards, alerts for quality drift).
  • Training workshop for the team (2–4 hours).
  • Warranty support for 3 months after launch — as part of our quality certificate.

We have completed 30+ projects in generative AI — this gives us the right to guarantee results.

How Is the Generative AI Development Process Structured?

  1. Analysis (1–2 days): audit of current architecture, clarification of use case, selection of models and success metrics. We evaluate the project free of charge.
  2. Proof of Concept (1–3 weeks): quick prototype on your data — to see real quality, not blog demos.
  3. Design (1–2 weeks): pipeline architecture, infrastructure (GPU cluster/API), A/B testing plan.
  4. Implementation and fine-tuning (4–12 weeks): development, LoRA/full fine-tuning, integration with queue and cache.
  5. Testing (1–2 weeks): load tests, metric validation, edge-case verification (negative scenarios).
  6. Deployment and monitoring (1–2 weeks): production deployment, monitoring setup, documentation.
What We Verify at the Proof of Concept Stage
  • Alignment of expectations and actual generation quality (CLIP score, user study).
  • Inference speed at different batch sizes and GPU types.
  • Likelihood of toxic/incorrect generations — checking safety filters.
  • Scalability: will the model handle peak load.

Timeline Estimates

Integration of a ready API (DALL·E 3, Midjourney API, Stability API) — 1–2 weeks. Self-hosted pipeline with fine-tuning — 6–12 weeks. Full platform with UI, queues and monitoring — 3–6 months. The specific cost is calculated individually after analyzing your scenario.

Contact us — order a consultation, and we will select the optimal architecture for your project. Get a preliminary cost and timeline estimate for free.