161 results found

1. Prevent Lens Spamming

   With tools like Easy Lens and the latest AI technologies, creating and publishing lenses has become extremely fast and effortless. As a result, some creators are now releasing new lenses every hour, hoping for a “lucky viral” hit.

   This flood of low-effort content makes it much harder for high-quality, thoughtfully crafted lenses to gain visibility. Increasingly, I see genuinely impressive work receiving little to no reach simply because it gets buried.

   A straightforward way to address this issue would be to introduce limit on the number of lens submissions per creator in a certain period of time.

   14 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Lens categories not applying after publishing (Primary & Secondary remain blank)

   For the past ~3 months, I’ve been consistently facing an issue where lens categories are not applied after publishing.

   Regardless of the lens type (Game, 3D, ML, or Beauty), both Primary and Secondary categories remain blank on the published lens, even though the lens is live and public.

   This impacts:

   Lens discovery and reach

   Proper placement in the Games category

   Fullscreen game UX for game-based lenses

   Because of this, game lenses are not reaching the intended audience, and overall views have dropped significantly.

   This issue is occurring across multiple lenses, not just one, and seems to be unrelated to the lens content itself.

   Attaching screenshots for reference.
   Would really appreciate this being looked into or prioritized, as correct categorization is critical for publishing and discovering game lenses.

   Screenshot attached showing published lens with blank Primary & Secondary categories.

   For the past ~3 months, I’ve been consistently facing an issue where lens categories are not applied after publishing.

   Regardless of the lens type (Game, 3D, ML, or Beauty), both Primary and Secondary categories remain blank on the published lens, even though the lens is live and public.

   This impacts:

   Lens discovery and reach

   Proper placement in the Games category

   Fullscreen game UX for game-based lenses

   Because of this, game lenses are not reaching the intended audience, and overall views have dropped significantly.

   This issue is occurring across multiple lenses, not just one, and seems to be unrelated to the… more

   •  

   10 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   4 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   started  ·  AdminRaag Harshavat (Senior AR Developer Relations Specialist, Snap, Inc.) responded

   Hello all,

   
   

   We have removed the ability for users to specify tags. this was intended because our moderation team follows a categorization system and is the team that makes the determination.

   
   

   We are currently working on ways to make their designations more transparent and accurate. Feel free to leave more feedback on ways that you think we can do better and we will have updates soon.

3. Remove lenses that are same but have different Name/Previews

   We all have noticed a growing number of duplicate lenses being uploaded using identical or minimally modified files. This is especially common with popular concepts like Alien Face Sticker filters, Spiderman Masks filters, Blood Face filters, etc.

   This kind of spam reduces the overall quality of the platform and makes it harder for original creators to stand out.

   I’d suggest a few improvements,
   -Detect and remove duplicate or near-identical lens uploads
   -Issue warnings or restrictions for repeated spam uploads
   -Prioritise or highlight the original creator, possibly by upload date
   -Introduce a reporting system i.e. Google form, specifically for duplicate or spam lenses and possible original creator

   Many of these lens files are shared for learning purposes, not for mass re-uploading. Fixing this would possibly help new lenses to stand out.

   We all have noticed a growing number of duplicate lenses being uploaded using identical or minimally modified files. This is especially common with popular concepts like Alien Face Sticker filters, Spiderman Masks filters, Blood Face filters, etc.

   This kind of spam reduces the overall quality of the platform and makes it harder for original creators to stand out.

   I’d suggest a few improvements,
   -Detect and remove duplicate or near-identical lens uploads
   -Issue warnings or restrictions for repeated spam uploads
   -Prioritise or highlight the original creator, possibly by upload date
   -Introduce a reporting system i.e. Google form, specifically for duplicate or… more

   7 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Lock objects in Scene Hierarchy (prevent selection & transforms)

   It would be super helpful to add a “Lock” toggle 🔒 for Scene objects directly in the Scene Hierarchy.
   When an object is locked, it cannot be selected in the viewport and its transform (position/rotation/scale) can’t be edited avoiding accidental moves, especially for background / environment elements.

   In complex scenes, it’s very easy to accidentally select and move large background objects (BG, skybox planes, environment meshes, ...). A lock feature would significantly reduce mistakes and speed up editing!

   7 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   under review  ·  AdminRaag Harshavat (Senior AR Developer Relations Specialist, Snap, Inc.) responded

   Hey Yassin,

   
   

   Thanks for the report. We are going to discuss this issue internally and decide on what kind of action makes the most sense! Will update you when possible

5. 3D object tracking | Bounding Boxes to Real Objects

   Adding 3D object tracking.
   This will open up a multitude of possibilities for both community and branded lenses.

   Here's a link to a research project that fits the idea.https://facebookresearch.github.io/boxer/

   • 

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Feature Request: Dedicated Lens Studio IDE for Spectacles

   Developing for Spectacles within a mobile-first IDE creates unnecessary friction. Many mobile features are redundant or broken on the device, while essential Spectacles functions lack native integration.
   Key Issues
   • Feature Redundancy: Tools like Segmentation remain visible in the UI despite being unsupported, leading to developer confusion.
   • Lack of Native Parity: "Device Tracking - Surface Mode" doesn't work natively for Spectacles; we shouldn't need a separate placement package for a core spatial feature.
   • API Fragmentation: The shared API list is cluttered with mobile-only methods, making it difficult to identify Spectacles-compatible logic.
   Proposed Solution
   I am requesting a Spectacles-specific version of Lens Studio (or a dedicated "Native Specs Mode") that includes:
   1. A Streamlined UI: Automatically hides all non-functional mobile features.
   2. Native Surface Support: Built-in surface placement that works out-of-the-box for world-locked content.
   3. Dedicated Documentation: A standalone API reference strictly for Spectacles-supported features.
   At this stage, Spectacles development has evolved enough to deserve its own native environment and optimized workflow.

   Developing for Spectacles within a mobile-first IDE creates unnecessary friction. Many mobile features are redundant or broken on the device, while essential Spectacles functions lack native integration.
   Key Issues
   • Feature Redundancy: Tools like Segmentation remain visible in the UI despite being unsupported, leading to developer confusion.
   • Lack of Native Parity: "Device Tracking - Surface Mode" doesn't work natively for Spectacles; we shouldn't need a separate placement package for a core spatial feature.
   • API Fragmentation: The shared API list is cluttered with mobile-only methods, making it difficult to identify Spectacles-compatible logic.
   Proposed Solution
   I am requesting a Spectacles-specific… more

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Followed Creators Category in Lens Explorer

   It would be great to add a new category in the Lens Explorer dedicated to “Followed Creators.”
   Currently, even if we follow creators, it’s difficult to keep up with their latest lenses, especially if they don’t post stories frequently. This makes it easy to miss new content.
   Having a dedicated section for followed creators would help users quickly discover and access new lenses from their favorite creators, improving both user experience and creator visibility.

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Transparent Justification for Lens Restrictions

   Creators should be given a clear and specific reason whenever a Lens is flagged for not meeting Submission Guidelines, failing Creator Rewards criteria, or being otherwise restricted. Too often, these limitations are applied without justification, leaving creators frustrated and in the dark.

   4 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   under review  ·  AdminKalen Beacham (Product Manager - Lens Creator Success, Snap, Inc.) responded

   Good day! Thank you for sharing this feedback. For providing more clarity around the submission guidelines, this is something we are actively reviewing and working on to facilitate more transparency. As for Creator Rewards, we understand the concerns and will look into it further.

9. AI Portrait for Camera Kit

   For now AI Portrait work on Snapchat app but not on web (even official Snap WebAR Link) and neither on iOS app using Camera Kit.
   This would be a very nice feature to have 🤞

   6 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Multiple Scenes

    Lens Studio would benefit enormously from true multi-scene support for game and app development workflows.

    Right now, larger projects are forced into one giant scene or awkward prefab-based workarounds. There was a Scene Manager system in the past, but it relied on scene-sized prefabs, was difficult to maintain, and has since been deprecated. For developers trying to build games or more complex interactive experiences, proper scenes would be a major quality-of-life improvement.

    Why scenes matter

    1. Clean restarts / state resets
       Reloading a scene is one of the simplest ways to reset gameplay state. Without scenes, developers often need to manually reset every variable, timer, spawned object, enemy state, UI state, etc. That becomes messy fast.

    2. Better project organization
       Separate scenes for:

    Main menu
    Tutorial
    Gameplay
    Pause menu
    Results screen
    Different maps / levels
    Testing environments

    This keeps projects cleaner and easier to maintain.

    1. Loading & performance optimization
       Only load what is needed. A menu scene should not need gameplay assets loaded. A small tutorial scene should not carry a full boss fight’s content in memory.

    2. Team collaboration / Git workflows
       Multiple developers working in one project can work on different scenes rather than constantly touching the same master scene file and causing merge conflicts.

    3. Multiple levels / experiences
       Some experiences naturally need multiple spaces or levels. While dynamic instantiation is useful, forcing everything into runtime spawning is often slower to build, harder to debug, and less intuitive than authoring levels directly.

    4. Faster iteration & testing
       Jump directly into a combat test scene, UI sandbox, or performance benchmark scene without loading the whole project.

    About persistent data between scenes

    A concern raised is “how do you know what carries over?”

    That is already solved in many engines:

    Default behavior: scene-local data is destroyed on load
    Optional persistent/global objects for intentional carryover
    Explicit saved state systems
    Developer-controlled scene transitions

    This is a feature, not a problem. Many developers want scene changes to clear state by default.

    Suggested implementation
    Additive or single-load scene options
    Persistent global manager objects
    Async scene loading
    Scene transition callbacks
    Build settings / scene order list
    Editor play-from-selected-scene support

    Lens Studio would benefit enormously from true multi-scene support for game and app development workflows.

    Right now, larger projects are forced into one giant scene or awkward prefab-based workarounds. There was a Scene Manager system in the past, but it relied on scene-sized prefabs, was difficult to maintain, and has since been deprecated. For developers trying to build games or more complex interactive experiences, proper scenes would be a major quality-of-life improvement.

    Why scenes matter

    1. Clean restarts / state resets
       Reloading a scene is one of the simplest ways to reset gameplay state. Without scenes, developers often need to manually… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Control 3D Bitmoji with 3D Body Tracking

    Currently we can import Mixamo animations or create our own to animate a Bitmoji character.

    We can also use 3D Body Tracking to drive a rigged 3D character.

    However I can't find an easy way to drive a 3D Bitmoji character with 3D Body Tracking.

    The 3D Body Tracking documentation says it's possible and references the Bitmoji 3D doc, but there's nothing there.

    https://developers.snap.com/lens-studio/features/ar-tracking/body/body-templates/3d-body-tracking#adding-a-character

    https://developers.snap.com/lens-studio/features/bitmoji-avatar/bitmoji-3d

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Prefab utilities

    In each component allow to
    Apply to prefab - save changes to only this component onto the prefab
    Revert to prefab (if component already exists on prefab)- revert only this component to the saved prefab

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Feature Request: Marketplace for Lens Studio

    I would like to suggest the addition of a Marketplace within Lens Studio.
    This feature would allow creators to:
    • Share, buy, and sell assets such as scripts, shaders, materials, and templates.
    • Access a wide library of ready-made components to speed up development.
    • Collaborate and exchange resources within the creator community.

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Support for SPZ format Gaussians

    Would love to request native support for the .spz format for Gaussian Splats in Lens Studio in addition to .ply. SPZ is rapidly becoming an emerging industry standard with platforms and tools like Niantic Scanniverse and Marble Worlds adopting it for more optimized storage, faster loading, and better streaming workflows. Native SPZ support inside Lens Studio would greatly improve interoperability, reduce conversion friction, and make it much easier for creators to bring real world Gaussian captures directly into Spectacles and SnapAR experiences

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Fix: getComponent(SomeClass.getTypeName()) bug

    getComponent(SomeClass.getTypeName()) seems to not be checking the numbers after the colon ":" in the getTypeName() string!

    When the string is the same before the colon for multiple components on the same SceneObject, it can return the wrong component. Been running into this a couple times and it took a while to figure out what the issue was.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Nearby AR Experience Discovery (Landmarkers & Custom, Image Tracking & AR Mirrors)

    A feature that lets Snapchat users discover AR experiences nearby — including Image Marker Lenses, Landmarker/Custom Landmarker Lenses, and AR Mirrors built with Camera Kit. When users are near an active experience, they’d receive a smart notification or in-app prompt to explore it.

    This would help brands and creators increase visibility for real-world AR activations while connecting digital creativity with physical locations.

    5 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Matcap Shader Error

    Hi, I believe there's an error with the matcap reflection node available in the shader editor. When the camera rotates in the Z axis, the reflections rotate as well, which I believe shouldn't happen.

    I think the error is in line 25:
    vec3 right = normalize(cross(forward, system.getCameraUp()));

    I believe it should be
    vec3 right = normalize(cross(forward, vec3(0.0, 1.0, 0.0)));

    because otherwise the camera up vector changes when the camera rotates

    •  

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Material Blend Modes Resources

    I've been struggling with the large choice of BlendModes, particularly how they affect the final look of the materials accross different devices, particularly 2024 Spectacles. I’d love to make an empirical tutorial on them, but because the Lens Scripting API documentation currently doesn't provide information on their exact expressions https://developers.snap.com/lens-studio/api/lens-scripting/enums/Built-In , I’d run the risk of providing inaccurate or confusing information.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Zip option in menu should retain lens icon

    The option to share as zip in the menu currently does not include the icon.png. You can simply add it back into the zip to make it work but it seems best this is updated to properly keep the icon in the zip file.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Bug: Custom Location Mesh clears Custom Location Asset input

    When removing the Cache folder, the Custom Location Asset input is cleared, making the Custom Location Mesh stop rendering

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating