# Best practices for a good filter

> Guidance for designing a filter in Nosmai Studio that looks good and runs well: keep beauty subtle, size assets for a phone, check every frame shape, watch performance as you build, and record a clear preview. These habits keep a filter smooth on real devices and presentable in a store listing.

> For AI agents: the complete documentation index is at https://nosmai.com/llms/studio.txt

Product: Nosmai Studio
Group: studio-get-started
Source: https://nosmai.com/docs/studio/get-started/best-practices/



## Overview

A filter is authored on a desktop but runs on a phone, in front of a real face, in
a store listing. These habits keep it looking good and running well everywhere it
ends up.

**Product:** Nosmai Studio · **Platform:** macOS, Windows · **Updated:**
7 October 2026 · **Reading time:** 6 minutes

## Keep beauty subtle

Maximum beauty looks artificial on a real camera. Start low and raise only until it
reads: skin smoothing around `0.25` to `0.40`, teeth around `0.15` to `0.30`. Skin
smoothing is the most expensive beauty stage, so it is both the look and the cost to
watch. See [Beauty and makeup](/docs/studio/guides/beauty-and-makeup/).

## Size assets for a phone

- Resize textures to the smallest edge that still looks right. A 4096 pixel texture
  is a memory and bandwidth risk on a phone.
- Decimate dense 3D models toward 150,000 triangles or fewer.
- Prefer one shared atlas over many separate textures.

The numbers behind these are in
[Limits and technical guidelines](/docs/studio/reference/limits/).

## Check every frame shape

A filter ships to phones, tablets, and desktop webcams. Use the target aspect
control (9:16, 16:9, 1:1, 4:5) and the safe-area overlay to confirm the effect
survives each shape, so a hat does not drift off a square crop. See
[Preview your filter](/docs/studio/guides/preview-your-filter/).

## Watch performance as you build, not at the end

Open the Performance view regularly, not just before export. The by-layer breakdown
shows which piece is expensive while you can still change it cheaply. Author on the
Full FaceMesh model when you want behaviour closer to a phone. See
[Check performance](/docs/studio/guides/check-performance/).

## Test on a real device

The Studio preview is close to a phone but not identical, and a game only runs on a
device at all. Connect a phone and preview there before you consider a filter done.
See [Preview on a device](/docs/studio/guides/preview-on-a-device/).

## Make a clear preview

The preview video and poster you export are what a person sees before trying the
filter. A good one:

- Shows the effect quickly, in the first second or two.
- Is well lit, with the face centred.
- Demonstrates any reaction (a blink, a smile) so the interactivity is obvious.
- Uses a length that fits the effect: short for a simple look, longer for a game.

Choose the preview length and poster frame in the export dialog. See
[Export a package](/docs/studio/publishing/export-a-package/).

## Keep the project tidy

- Remove layers and assets you are not using, so the package stays small.
- Name things clearly, especially text slots a script writes.
- Keep the filter's ID stable across versions, so an update replaces rather than
  duplicates it.

## Next steps

- [Make your first filter](/docs/studio/get-started/make-your-first-filter/)
- [Check performance](/docs/studio/guides/check-performance/)
- [Preview on a device](/docs/studio/guides/preview-on-a-device/)

## Reference

- [Limits and technical guidelines](/docs/studio/reference/limits/)
- [Current limitations and roadmap](/docs/studio/reference/limitations/)
