Documentation

Everything we publish, in the order a team actually needs it: what the product does, what source imagery it works from, what comes out, what happens to a shopper's photograph, and how it attaches to a storefront.

Reference

API and integration architecture

The rendering pipeline, how the try-on attaches with one asynchronous script tag, the REST API for headless storefronts, and the security posture.

Read →
Reference

Image requirements

What makes a good source photograph, what the shopper supplies, and what comes back: up to 4K in PNG, WebP or JPEG.

Read →
Reference

Security and data handling

What happens to a shopper's photograph, how long it exists, where the service runs, and what Viewrobe does and does not certify.

Read →
Background

What is VTON

The technology explained: how the pipeline works, how it differs from AR and 3D, and how to evaluate output quality properly.

Read →
Background

Use cases by sector

Bridal and occasion wear, fashion e-commerce, made-to-measure tailoring, and lookbook and catalogue production.

Read →
Background

Company

Who Viewrobe is, where it is, and the legal entity behind the contracts.

Read →

Evaluating before you integrate

Nothing here needs to be taken on trust. The useful order is: send a handful of your own product photographs, including the awkward ones, and a range of real shopper photographs; look at the output against the checks on the what is VTON page; then look at integration. A system that holds up on your own worst flat-lay is the only evidence that counts.

Integration specifics for a particular storefront, and any figures tied to volume, turnaround or commercial terms, are confirmed directly rather than published here, because they differ by deployment.

See it on your own catalogue

Book demo