Nosmai Studio Limits and technical guidelines
Nosmai Studio / Reference / Limits and technical guidelines
Updated October 6, 2026

The performance thresholds Nosmai Studio checks a filter against, and the guidance behind them: texture size, triangle count, package size, render passes, and minimum SDK version. These are tuned for a mid-range phone, because a filter authored on a desktop has to run on a phone. Staying under them keeps a filter smooth.

Overview

The thresholds Nosmai Studio uses to judge a filter in the Performance view, with the reasoning. They are tuned for a mid-range phone. Treat them as guidance, not hard caps: the Performance view warns, it never blocks export.

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

Performance thresholds

Each resource reads Good, Warning, or High against these bands:

ResourceWarning atHigh atWhy
Largest texture edge2048 px4096 pxLarge textures cost GPU memory and bandwidth on a phone
Texture memory (decoded)64 MB192 MBThe uploaded footprint competes with the host app for GPU memory
Package size10 MB30 MBA large package is slower to download and decrypt before the filter runs
Total triangles150,000500,000High vertex counts raise per-frame cost on a mid-range GPU
Render passes per frame2640Each pass is a full render-target bind and draw; passes include the engine's own stages
Fill (kilopixels per frame)28,00060,000Fill rate is the main cost on integrated and mobile GPUs

Render passes count every framebuffer the engine binds in a frame, including its fixed pipeline (source, face mesh, each beauty stage, composite), not just your own shader passes. A plain beauty-and-overlay filter sits around 12 to 16 passes before you add anything.

Supported inputs

SettingValues
Preview target aspectsSource, 9:16, 16:9, 1:1, 4:5
FaceMesh modelLite (default) or Full
Minimum SDK versionDefault 3.0.0; set per filter at export

Supported file formats

See File formats for the import and export format tables.

Guidance

  • Start beauty smoothing low (0.25 to 0.40). It is the most expensive beauty stage.
  • Resize textures to the smallest edge that still looks right; a 4096 texture is a phone risk.
  • Decimate dense models toward 150,000 triangles or fewer.
  • Combine full-frame shader passes where you can; fewer passes means less fill.
  • Check the Performance view before every export, especially on the Full FaceMesh model, which is closer to phone behaviour.

Next steps

Nosmai

An AR and AI company. Founded on the idea that the next decade of software will be visual, and that the tools for it should be within reach of anyone building.

Newsletter

Product updates and release notes. No spam.

© 2026 nosmai, inc · all rights reserved