Skip to main content

Publishing Your Lens

Publish your SPECS Lens through the SPECS Developer Portal: upload its build from Lens Studio, create a release, complete its store listing, submit it for review, and release it to Lens Explorer.

You publish SPECS Lenses through the SPECS Developer Portal. There you create a record for your Lens, upload its build from Lens Studio, and create a release: a version of the Lens with its store listing, which you submit for review. Once the release is approved, you release it, and users can find it in Lens Explorer.

Before you publish a SPECS Lens

  • A SPECS account with access to the Developer Portal. If you're new to SPECS, the portal guides you through creating an account and an organization when you first sign in.
  • A Lens Studio project whose Target Platform is SPECS. See Configuring Project Settings.
  • A Lens of 25 MB or less that doesn't use Experimental APIs.
  • A package ID for your Lens, such as com.example.mylens: at least two lowercase segments separated by dots, each starting with a letter and using only letters, numbers, and underscores, 128 characters at most. It has to be unique: you can't use a package ID that already belongs to another Lens. Lens Studio's default, mylens, isn't valid.
  • A Lens icon in your project. The icon is packaged in the build, and the SPECS Developer Portal rejects a build without one. See Creating an Icon.
  • For a Public release, a Privacy Policy and Terms of Service for your Lens, as HTTPS links or text. You add them in the portal, under the Lens's Settings > Legal documents. An Internal release doesn't need them.
  • If your Lens uses Commerce Kit, product IDs that start with your package ID.
  • At least one preview image or video of your Lens, for its store listing. See Lens Explorer Asset Requirements.

Publish with CLAD

If you build with CLAD, ask your agent to publish your Lens. The /specs-publish skill takes a SPECS Lens to "submitted for review": it checks the project, proposes what's missing (package ID, Lens name, icon, signing key, build version, store listing, content rating, and preview media), asks you to confirm once, then exports, uploads, and submits the release. See CLAD Agents and Skills.

To publish by hand, follow the steps below.

Create your Lens in the SPECS Developer Portal

  1. Go to the SPECS Developer Portal and sign in with your SPECS account. If you belong to more than one organization, switch to the one that should own the Lens: the selected organization decides where the Lens is created and who can manage it.
  2. On the Lenses dashboard, select Create New Lens.
  3. In Lens Name, enter the name Lens Explorer shows for your Lens.
  4. In Package ID, enter your Lens's package ID, and wait for it to validate. If it's already in use, choose another.
  5. Select Save.

The Lens's page opens, with the Overview, Releases, Builds, Monetization, and Settings tabs.

Upload your SPECS Lens's build from Lens Studio

  1. In Lens Studio, open Project Settings and select Platform Settings > SPK Settings.
  2. Enter the same Package ID you entered in the portal, set the Build Version in major.minor.patch format (such as 1.0.0), higher than any version you've published, and create or assign the Signing Key. See Configuring Project Settings.
  3. Clear every item under Please fix the following settings before publishing.
  4. Select Publish, and follow the prompts to upload the build.

When the upload is complete, Lens Studio opens the Developer Portal for your Lens. The build appears in the Builds tab.

The Publish button at the top right of the Project Settings window, with Target Platform set to SPECS

You can also upload the build from the portal: in the Builds tab, select Upload build, choose the Lens's .spk file or drag it into the upload area, and select Upload.

SPECS build states

StateWhat it means
UploadedThe portal received the file; processing hasn't started.
ProcessingThe portal is validating the build.
ValidatedThe build passed validation, and you can attach it to a release.
RejectedThe build failed validation. Review the error, and upload a new .spk.
ErrorAn unexpected error occurred. Review the error, and upload a new .spk.

Create a release of your SPECS Lens

  1. In the Lens's Releases tab, select New Release.
  2. In Release Name, enter a version number in X.Y.Z format, such as 1.0.0. It has to be greater than your highest release version so far.
  3. In Start Store Preview From, start from a blank store listing, or copy the listing from an earlier release.
  4. In Build, choose a validated build. You can attach it later, but you need one before you submit the release.
  5. Select Create Release.

The submission flow for the release opens.

Submit your SPECS Lens for review

To open the submission flow later, select the draft release in the Releases tab, and select Submit for Release.

  1. Build: check the release version and that a validated build is attached. If none is, attach one from Available Builds, or select Upload New Build. Select Continue.
  2. Store listing:
    1. Check the icon. The portal uses the icon packaged in your .spk; you don't upload one.
    2. In Store Media, upload at least one preview image or video. See Lens Explorer Asset Requirements.
    3. Confirm or edit Lens Name, 30 characters at most.
    4. Add a Description of at least 10 characters.
    5. Add one to five Tags, from the portal's list: #Outdoors, #Active, #Offline Mode, #Beginner Lenses, #Educational, #Tabletop, #Productivity, #Wellness, #Holiday, #Travel, #Creative, #World-Based, #Watch, #Music, #Lifestyle, #Tools, and #Developer Tool.
    6. Select a Primary Category, and optionally a Secondary Category.
    7. Answer the content-rating questions. They set the Lens's age rating: 13+, 16+, or 18+.
    8. Select Continue. The portal saves the store listing.
  3. Regions & distribution: in Distribution, choose who the release is for:
    • Public: users outside your organization, after review and approval.
    • Internal: only users in your SPECS organization, for example to test before a public release.
  4. Review & submit: review the summary, fix anything listed under Cannot submit, and select Submit for Review.

The release moves to the In review group of the Releases tab. Snap reviews it for compliance with the Submission Guidelines.

Designing your SPECS Lens's store media

  • Show the function of the Lens. Users who see the preview in Lens Explorer should understand what the Lens does when they open it.
  • Include people in the frame for connected Lenses, wearing SPECS, to show which Lenses people can use together.
  • Use bright colors. Black appears transparent, and dark colors can be hard to see.
  • Keep the background uncluttered, so the Lens's elements stand out. Prefer a blank background unless the location or placement matters.
  • Avoid text. The tile is small, and the Lens and creator names are already overlaid.

Release your approved SPECS Lens

When the review approves your release, it moves to the Ready to publish group.

  1. In the Releases tab, select the approved release, and select Release.
  2. Choose the release channel: Public, for public delivery, or Internal, for users in your SPECS organization only.
  3. Choose Release immediately, and select Release Now.

Once the release is live, the Overview tab shows it with its store listing.

Congratulations on publishing your Lens! Take a capture and share your Lens with the community on the r/Spectacles subreddit.

Set whether users can discover your SPECS Lens

Visibility applies to the whole Lens, not one release.

  1. In the Lens's Settings tab, under Lens visibility, choose:
    • Listed: users can discover and use the Lens.
    • Unlisted: only users with a direct link can open the Lens.
  2. Select Save Settings.

To share an unlisted Lens, copy its Lens Store link from the Settings tab, or share its QR code.

Getting your Lens into Lens Explorer

Snap reviews every Lens before it's published in Lens Explorer. Lenses that meet these requirements can be published there:

  • The Lens has a defined objective. When it opens, it shows visuals that indicate what to do.
  • The Lens follows the design best practices and feels performant (45 FPS).
  • The Lens is free of crashes and bugs.
  • The Lens has a custom icon and a preview image.

The Featured category showcases compelling Lenses that set the bar for quality and show what's possible on SPECS. The category is refreshed regularly as new Lenses are published and updated.

Snap curates the featured Lenses on these factors, which all add up to an experience users love.

Must-haves

  • User experience: the Lens is intuitive, straightforward to navigate, and gives the user value. Interactions feel natural and responsive.
  • Completeness and depth: the Lens feels complete and gives recurring value. If it tells a story, the story has a beginning, middle, and end, and a way to repeat.
  • Design and polish: the Lens is visually appealing and polished, with attention to detail in both looks and function.

Other considerations

  • Innovation: the Lens gives unique value and pushes the bounds of what's been done with AR. It inspires other developers to explore new ideas.
  • Popularity: the Lens is already proving valuable to the SPECS community.

AR Lens developer checklist for SPECS

  1. Frame rate and performance
    • Target 45 FPS at all times. A frame rate under 45 FPS is a good sign that the Lens is over its power budget.
    • Check the frame rate, CPU and GPU use, and thermal readings live on the device with the Lens Performance Overlay before you submit.
    • For draw calls, shaders, mesh efficiency, and update loops, see Optimizing Lens Performance.
  2. File size
    • The published Lens must be 25 MB or less.
    • Use cloud storage or compressed assets when you need to.
  3. Power and thermal budget
    • Track power, thermal load, and memory, and record Perfetto traces, with the SPECS Monitor.
    • Stay within Snap's recommended power and memory budget, to avoid thermal throttling and the frame drops that persistent high CPU or GPU load causes (for example, frequent updates, physics, or real-time lighting).
    • Going over the budget limits how long the experience can run: the device enters thermal standby to cool down before the battery runs out. The experience may still run, but its reduced performance and runtime affect the user.
  4. Crashes and stability
    • Include a visible version number, and log "Lens Opened: vX.X.X" on startup.
  5. Debug and test mode (recommended)
    • Provide a debug menu and in-Lens tests, so teams can check individual Lens states and logic paths as you make changes.
  6. On-device testing
    • Always test the Lens on SPECS after you make changes and before you submit, to avoid issues and shorten turnaround: emulators don't reflect the full performance or thermal behavior.
    • Share the list of tests you ran, and the test steps Snap should run, with your submission.
  7. Capturability
    • Use components that can be captured by default, unless you've agreed with Snap to use one that isn't supported.
  8. Version visibility and logging
    • Show the version number on launch, in the start-up prompt or the UI. It helps with troubleshooting.
    • Log the version number on startup, to help troubleshoot bug reports.
  9. Metadata for every submission
    • A preview image or video in Store Media
    • A custom icon
    • A concise description of what the Lens does
    • Release notes: what changed, issues fixed, known issues, and features added
  10. Design and UX best practices
    • Follow the SPECS design principles:
    • Use the latest recommended assets, such as Interaction Kit and UI Kit.
    • Minimize user fatigue: optimize for posture, hand gestures, and shifts of attention.
    • Make content legible, and place it at a comfortable depth.
    • Keep effects close to the real world, but not cluttered.
    • Use sound as well as visuals.
    • Add onboarding, and consider the Lens's story line.
    • Agree on whether the Lens needs a demo mode for events.

Troubleshooting publishing a SPECS Lens

  • You can't sign in to the portal. Check that your SPECS account has access to the Developer Portal.
  • The portal sends you to SPECS Accounts. Finish setting up your organization there, then return to the Developer Portal.
  • Create New Lens fails. Check the package ID: it has to match the required format and be available.
  • The build can't be submitted. Wait until it's Validated. If it's Rejected or Error, review the build's error and upload a new .spk.
  • Submit for Review is unavailable. Review the Cannot submit list. Common causes are a missing validated build, missing store media, a description under 10 characters, no tags, no primary category, or no region availability.
  • A Public release asks for legal documents. Add a Privacy Policy and Terms of Service in the Lens's Settings > Legal documents, as HTTPS links or text, and wait until they finish processing. They apply to every version and channel of the Lens.
  • The build is rejected for a missing icon. Set a Lens icon in Project Settings > Distribution Settings > Lens Icon, raise the Build Version, and upload again.
  • You can't select Private visibility. Choose Listed or Unlisted.
  • You can't select a manual or scheduled release. Choose Release immediately.