One Lens, three channels:
how Snap Camera Kit changes the AR production model

What Camera Kit actually is

Most people think of Snap as a social platform. Camera Kit is a different product: it is Snap's SDK for running Lenses outside of Snapchat. A Lens built in Snap Lens Studio can be packaged and deployed to three distinct surfaces using Camera Kit, with no additional creative production.

The three surfaces are: Snapchat itself (standard social lens, discoverable, shareable), Camera Kit for Web (runs in a mobile or desktop browser via URL, no Snapchat account or app install required), and Camera Kit for Mobile (an iOS and Android SDK that embeds the Lens inside your own branded app, with full control over the surrounding UI).

The Lens is built once. The surfaces are three different ways to distribute it.

The three surfaces, compared

Surface	Access method	Snapchat needed?	Brand control
Snapchat AR	Snapchat app, Lens link or Snapcode	Yes	Lens creative only; Snap UI surrounds it
Camera Kit for Web	URL in mobile or desktop browser	No	Full page design; Snap powers the camera layer
Camera Kit for Mobile	Inside your own iOS or Android app	No	Full app context; no Snap branding required

Snapchat: social distribution, Snap's reach

Publishing to Snapchat gives the Lens access to Snap's discovery and sharing mechanics. Users can find it via Lens Explorer, share it directly to stories or chat, and the Lens benefits from Snapchat's existing audience. This is the awareness layer of the campaign: reach people where they already are.

Camera Kit for Web: no install, brand-owned URL

Camera Kit for Web loads the Lens in a standard mobile browser via WebRTC. The user taps a link or scans a QR code and the camera activates with the Lens running. No Snapchat, no app store, no download. This surface is useful for event activations (a QR on printed material leads directly to the AR experience), brand website campaigns, and audiences where you cannot assume Snapchat is installed.

The surrounding page is fully yours to design. The Lens runs in a container your team controls, branded however the campaign requires.

Camera Kit for Mobile: your app, Snap's engine

Camera Kit's mobile SDK lets you embed the Lens inside your own iOS or Android app. The Snap Lens engine runs inside your app, but the user never sees Snapchat. Your brand's UI, your analytics, your user flow. This is the right surface when a brand already has an owned app and wants a premium AR experience integrated into it, not a separate Snap-branded moment.

Combined with the web and social surfaces, this means a single Lens can power an in-app try-on feature, a website AR moment, and a Snapchat lens campaign without separate 3D production for each.

What is the same across all three surfaces

The Lens file is identical. The 3D assets, animations, face tracking logic, object tracking, scripting, and interaction behaviour built in Lens Studio run the same way whether the Lens is in Snapchat, a browser, or a custom app. There is no porting step, no re-optimisation pass for each surface.

Most Lens Studio features work in Camera Kit. Face effects, body tracking, hand tracking, world AR, and custom scripting all carry over. The features that do not are Snapchat-specific social mechanics: Bitmoji integration, Friendmoji, and anything that depends on Snap's friend graph. Most brand campaign Lenses use none of these, so the cross-surface capability applies cleanly.

What changes per surface

Distribution is different. Sharing behaviour is different. The analytics source changes from Snap's dashboard on the social surface to your own analytics on Web and Mobile. The surrounding UI is yours to build on Web and Mobile, and Snap's on Snapchat.

This is not additional production work for the Lens itself. It is the integration work: embedding Camera Kit for Web in a brand landing page (a day or two of front-end work), or integrating the Camera Kit Mobile SDK into an existing app (typically two to five days depending on your app's architecture). The Lens creative is not touched.

When Camera Kit is the right call

Camera Kit is the strongest fit when Snap is already in the media plan and the campaign needs to extend beyond Snap's audience. A brand running a Snapchat Lens campaign for a product launch, for example, can use the same Lens on the product page via Camera Kit for Web and inside a retail app via Camera Kit for Mobile, without commissioning new creative for each.

It also makes sense when the brand does not want multiple AR production budgets but needs owned-channel presence alongside social. One Lens covers both.

When it is not the right call

If the brief requires something Lens Studio cannot do, or requires a different AR experience on each surface (a face filter on Snap, a product configurator on the website, a navigation feature in the app), Camera Kit does not help. In that case, you are building three different experiences, and the tooling question is separate for each.

Camera Kit for Mobile also requires a licensing agreement with Snap, which means it is typically an enterprise or partner path rather than something available to every small project. For a broader view of how Snap, WebAR, and native app decisions compare, see our platform choice guide.

How to brief for a Camera Kit campaign

Three questions determine whether Camera Kit is the right architecture and what the integration scope looks like:

• Which surfaces does the campaign need? Snapchat only, or Snapchat plus web, plus app? Each additional surface adds integration work, not creative work. Know the surface list before production starts.
• Does the brand have an existing app for Camera Kit for Mobile? Camera Kit for Mobile makes most sense when there is already an app to integrate into. If the app needs to be built from scratch, assess whether the AR feature justifies that scope.
• What is the core Lens interaction? Describe it in platform-agnostic terms: the user points the camera at X, Y happens. If that interaction works on Snap, it will work on Web and Mobile via Camera Kit. If it depends on Snap social features (Bitmoji, sharing into chat), note that those will not carry to the other surfaces.

Frequently asked questions