On the product page, shoppers see the garment on a model, on a mannequin or laid flat on a white background. The question in their head is a different one: how would it look on me? Until they get an answer, doubt remains, and doubt leads to putting off the purchase or ordering with a return already in mind.
Virtual try-on exists to answer that question. There are several approaches, and they do not all ask the same effort of the shopper. In this article we look at how photo-based try-on works, what it needs to give good results, which privacy questions to ask and when it makes sense to introduce it.
People buying fashion online are not only looking for technical details. They are trying to picture themselves wearing the item. The questions they ask are simple and very personal:
Catalogue photos, even good ones, only partly answer these questions. They show the item at its best, but on someone else. Virtual try-on tries to close that gap.
The term virtual try-on covers solutions that are quite different from one another. Broadly speaking, there are three routes.
The strength of photo-based try-on is simplicity. Shoppers do something they already know how to do, which is choosing a photo of themselves, and they see the result on their own image. For many shops it is the most natural starting point, because it asks shoppers to learn nothing new.
It is worth being clear about what it does not do: a generated image shows how the garment looks when worn, it does not replace a size recommendation. Size needs a dedicated tool that works from the garment's measurements.
The quality of the result depends a lot on the source images. You do not need special shoots, but a few precautions help a great deal.
It is also worth giving shoppers a few tips for their own photo: full length or a clearly visible upper body, good light, a front-facing pose and clothing that is not too bulky. Two lines next to the upload button are enough.
With photo-based try-on, shoppers hand you an image of themselves. That is personal data and needs careful handling. Before choosing any solution, ours included, make sure you have clear answers to these questions:
Get the answers in writing and pass them on to shoppers in plain language. A clear explanation next to the photo upload builds trust and removes doubts.
Photo-based try-on is not equally useful for every catalogue. It makes most sense in certain situations:
As with any tool on the product page, the effect should be measured. Our advice is to start with an A/B test on part of the catalogue or traffic and look at conversions, time on page and returns together, keeping in mind that returns arrive weeks after purchase.
FitFlow is the We Wear photo-based virtual try-on. It needs only two images: the product image and the shopper's own photo. The AI generates a photorealistic image of the shopper wearing the garment. There are no measurements to enter, no avatar to configure and no AR camera to switch on.
FitFlow runs in the browser, on mobile too, with no app to install. It works from the product feed you already have, such as your Google Shopping or Meta feed or a CSV file, so there is no separate catalogue to prepare.
It can be used alongside SizeFlow, our size recommendation tool: FitFlow shows how the item looks, SizeFlow says which size to choose. Together the two answers cover the shopper's main doubts on the product page.
If you would like to see FitFlow on your own products, book a 30-minute demo.
It is a system where shoppers upload a photo of themselves and receive an image of themselves wearing the chosen item. They do not enter measurements, configure an avatar or use a live camera.
Clean packshots on a plain background work best, with the whole garment in frame, one item per image, neutral light, accurate colours and good resolution.
FitFlow needs only two images, the product image and the shopper's own photo, and the AI generates a photorealistic image of the shopper wearing the garment. It runs in the browser on mobile too, with no app, works from the product feed (Google Shopping, Meta, CSV) and can be used alongside SizeFlow for size.