Nosmai Studio What happens after export
Nosmai Studio / Publishing / What happens after export
Updated October 6, 2026

After Nosmai Studio exports a .nosmai package, the filter reaches an app through the Nosmai SDK or through Cloud Filters. Studio does not publish to an app itself: it produces the package file, and a developer or the Nosmai Console takes it from there. This page explains where an exported filter goes and how it is updated.

Overview

Export produces a .nosmai package. From there the filter reaches an app in one of two ways: bundled with the app through the Nosmai SDK, or delivered at runtime through Cloud Filters. Studio itself does not publish to an app: it writes the package, and a developer or the Nosmai Console takes it on.

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

The two delivery paths

  • Bundled with the app. A developer adds the .nosmai file to their project and loads it with the Nosmai SDK. The filter ships inside the app build.
  • Cloud Filters. The package is hosted and delivered to the app at runtime, so a filter can be added or updated without a new app release. The app requests it by its filter ID.

Which path a filter takes is decided by the team building the app, not in Studio. Because of this split, you can design a filter without knowing in advance where it will run.

How a filter is identified

The package carries the distribution metadata you set at export: a display name, an ID, a version, an author, and a minimum SDK version. The ID is how an app and a catalogue refer to the filter. Keep the ID stable across versions of the same filter. See Distribution metadata.

Updating a filter

To release a change:

  1. Open the filter's project in Studio and edit it.
  2. Raise the version in the export dialog (for example 1.0.0 to 1.1.0).
  3. Keep the same ID so the update replaces the previous version rather than creating a new filter.
  4. Export again and hand the new package to the same delivery path.

A filter delivered through Cloud Filters can be updated without shipping a new app build; a bundled filter updates when the app does.

Verify it worked

  • The exported package carries the ID, version, author, and minimum SDK version you set.
  • An updated filter keeps the same ID and a higher version than the one it replaces.

Common problems

What you seeWhyFix
An update created a second filter instead of replacing the firstThe ID changed between versionsExport the update with the same ID as the original
A device loads an old version after an updateA bundled filter updates only with the appShip the update through Cloud Filters, or release a new app build
The app cannot run the filterIts minimum SDK version is higher than the app's SDKLower the minimum SDK version, or update the app's SDK
The filter is not available in the appIt has not been added to a delivery path yetA developer must bundle it or add it through the Nosmai Console

Next steps

Reference

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