General
Go to "My Assets" in the app. You'll see the current status of each upload there.
Streamfog updates automatically when you launch the app. No manual downloads needed.
Yes, but only on Apple Silicon Macs (M1 and newer). The Mac version supports browser source integration only — there is no virtual camera on Mac yet.
Join our Discord community for the fastest support, or email us at kev@streamfog.com for more detailed inquiries.
Setup
Streamfog offers two ways to integrate with OBS:
Browser source runs directly inside OBS and performs better. It requires a one-time setup (on Windows, Streamfog includes a patcher; on Mac, use the custom launcher).
Virtual camera works with any app — OBS, Streamlabs, Discord, Zoom, etc. — but uses more resources. Currently available on Windows only.
If you only use OBS, browser source is the recommended option.
Make sure to open the app you want to use the camera in AFTER Streamfog. Streamfog has to be running before you launch OBS, Streamlabs, Discord, etc.
Right-click your camera in your sources, click Properties, and set "Resolution / FPS Type" to Device Default. Then restart OBS.
Change the resolution in Streamfog to 720p @ 30fps.
Streamlabs does not support the browser source. Use the virtual camera instead. If you're on Mac, switch to OBS.
Your camera is most likely still active in OBS, Streamlabs, or another app. Important: hiding your original camera source is not enough — you need to deactivate or remove it entirely.
If you're using the browser source, your stream is unaffected — it runs independently inside OBS. If you're using the virtual camera, the feed will stop and show a green screen. Keep Streamfog open for the duration of your stream when using virtual camera.
Performance / Lag
Use the browser source method instead of virtual camera, and change the resolution to 720p. Your viewers won't notice the difference.
Lens Uploads
Usually 1–2 days, often faster!
The most common cause — especially if you used 3D modeling software outside of Lens Studio — is that your textures aren't saved as standalone files in the project. They may be embedded inside your 3D model file (e.g. an FBX), referenced from a folder outside your project, or never fully added as project assets. Everything looks fine on your machine because Lens Studio resolves them locally, but they don't travel with the project when you upload.
To fix: Open your Lens Studio project on the machine where it still looks correct. In the Asset Browser, right-click each 3D model and select Unpack. This extracts textures into your project as standalone files. Save and re-upload.
To prevent this in future projects from Blender:
- Go to File → External Data → Unpack All Into Files before exporting.
- Make sure each material uses only Image Texture → Principled BSDF → Material Output.
- When exporting FBX, set Path Mode to Copy and click the small box icon next to it to embed textures.
- After importing into Lens Studio, right-click the model → Unpack so textures become standalone project assets.
Your lens exceeds Snap's hard 8 MB processing limit. You'll need to simplify the lens and re-upload a smaller version.
To test locally, hit the Publish button in Lens Studio — you'll see the same error if it's still too large. Once you get it under 8 MB, save your changes before uploading.
This means your project took too long to load on our end. Make sure your project opens in under a minute during the "Loading Project" stage.
Also, after opening the project and waiting for it to load, check for a Tasks dropdown. If you see one, wait for all tasks to complete and the dropdown to disappear. Then save the project and re-upload.
We recommend Lens Studio 5.16.
Streamfog doesn't have a lens marketplace. You can create your own lenses in Lens Studio or hire an artist to build them for you.