> For the complete documentation index, see [llms.txt](https://docs.selvette.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.selvette.com/live-ar-makeup/preview-and-test.md).

# Preview and test Live AR

Test Live AR on a camera-capable phone before directing shoppers to it.

## Authoring preview

Use **Get QR codes** in the product's AR editor. The camera tuner is the best way to inspect color, finish, intensity, and coverage on a real face.

## Storefront test

1. Save the product and widget settings.
2. Open the live or preview product page on a phone.
3. Confirm that **Live try-on** appears and **Try it on** does not.
4. Open Live try-on and allow camera access.
5. Switch through every shade.
6. Confirm the shade name and selected variant match.
7. Add a shade to cart and confirm the correct variant reaches the cart.

## If Live try-on is missing

Check, in order:

1. the current plan includes AR;
2. the account has available credits;
3. the correct store and product are selected;
4. Live AR is enabled for the product;
5. at least one shade is authored; and
6. the device supports camera access and WebGL2.

See [Try-on, AR, or video unavailable](/troubleshooting-and-faq/feature-unavailable.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.selvette.com/live-ar-makeup/preview-and-test.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.