# How TryYourSize works

> From a tape measure to a size in your store's labels. What happens, who sees what, and what your store receives.

Source: https://docs.tryyoursize.com/get-started/overview/

TryYourSize recommends a size by simulating your garments on the shopper's own body. The shopper measures once, and the same body works in every store that uses TryYourSize.

## The flow

1. **Tape measurements.** The shopper enters a few measurements taken with a tape measure (height, weight and body measurements such as chest, waist and hip). They do this once, in our window, and can update them at any time.
2. **A body from the measurements.** Our engine builds a 3D body from those numbers alone, not from photos.
3. **Cloth simulation.** Your garment, as you described it in TryYourSize Studio (sizes, points of measure per size, grading and fabric), is simulated on that body in each size. For every size and zone the engine reports objective numbers: **ease** (room between body and garment, in cm), **contact pressure** (in kPa) and **fabric stretch** (%), and whether the size is **wearable**.
4. **A size.** The recommended size is the wearable size that best matches the fit your designer intended. It is returned in **your** size labels, through the product's size map ("M" → "Medium").

Many garments answer in under a second once they are published. The 3D view the shopper opens with "See it on you" then confirms the result on their own body.

## What your store receives

**Sizes only.** Your page, your app and your server receive the recommended size, the sizes that are wearable on this body, and whether the size has been confirmed by the full simulation. They never receive the shopper's measurements, their body, their email or their account. See [Privacy](https://docs.tryyoursize.com/guides/privacy.md).

## The pieces

| Piece | Where it runs | What it does |
|---|---|---|
| **TryYourSize.js** (web SDK) and the native SDKs | Your product page or app | Shows the size guide element, gives you the recommended size, opens our window |
| **The measuring window** | Our origin (`embed.tryyoursize.com`), framed in your page or shown in a native sheet | Sign-in, tape measurements, 3D try-on |
| **Studio** | `studio.tryyoursize.com` | Your catalog, garments, size maps, keys, origins, webhooks, results |
| **The server API** | `api.tryyoursize.com` | Catalog sync, orders and returns, server-side recommendations |

## Costs at a glance

A **fit check** is one shopper seeing a size for one product in live mode. The same shopper and product count once per 30 days. Test mode is never counted. A page view never starts a simulation: if a size is not available yet, the status is `unavailable` until the shopper asks for it. See [Going live](https://docs.tryyoursize.com/get-started/going-live.md) for billing.

## Next

- [Keys and modes](https://docs.tryyoursize.com/get-started/keys-and-modes.md): publishable, secret and restricted keys; test and live.
- Pick a quickstart: [Shopify](https://docs.tryyoursize.com/quickstarts/shopify.md), [Web](https://docs.tryyoursize.com/quickstarts/web.md), [React](https://docs.tryyoursize.com/quickstarts/react.md), [iOS](https://docs.tryyoursize.com/quickstarts/ios.md), [Android](https://docs.tryyoursize.com/quickstarts/android.md), [Server](https://docs.tryyoursize.com/quickstarts/server.md).