Launching today
Effects SDK helps developers add production-ready AI video and audio effects to web, desktop, and mobile apps. Add background blur, virtual backgrounds, smart framing, lighting correction, beautification, overlays, avatars, and real-time noise suppression — all running client-side, without sending video or audio to our servers.
Effects SDK
me thinks the effect collection looks useful for many apps? could lightweight quality settings help developers support more devices easily?
Effects SDK
@alheri_murya Absolutely! We provide several quality presets so developers can balance visual quality and performance depending on the user’s device. This makes it easier to support both high-end and lower-powered hardware with the same integration.
qq. can devs adjust the threshold levels for features like background blur intensity or noise suppression aggressiveness via the API? by the way congrats👏 for launching @maxim_troshin
Effects SDK
@priya_kushwaha1 Thank you! 👏 Yes, developers can adjust effect parameters through the API. Background blur intensity is configurable, noise suppression supports different sample rates and suppression strength levels, allowing developers to balance audio quality, performance, and processing aggressiveness.
me enjoyed seeing so many effects in one SDK. Could developers enable only selected features to reduce app size? That would make integration more flexible.
Effects SDK
@gaspard_dupuich Sure! The heaviest parts, such as AI models and WASM inference modules are loaded dynamically. So when a feature isn’t used, its related resources aren’t loaded, which helps reduce the initial app size and keeps the integration more flexible.
@anton_tushmintsev How do you decide when adding another effect is actually worth it?
Effects SDK
@anton_tushmintsev @ethanyoungl8 Let me answer for Anthony - he’s on the way 😁
Great question! We usually evaluate new effects from a few different angles:
We monitor larger platforms and follow the features they introduce. When we see a capability becoming widely adopted, we consider adding it to our SDK as well.
We regularly talk with customers to understand which features are in demand in their products. Some customers also request custom development for specific use cases, such as person-absence detection.
We brainstorm ideas internally, share them on our website and social channels, and collect feedback before investing heavily in development.
In the end, an effect is worth adding when we see clear user demand, a strong use case, and enough value across multiple products.
@maxim_troshin Have you had anyone choose a simpler solution instead of this and why?
Effects SDK
@aurther_bella We’re currently seeing two opposite trends.
On one side, some companies are moving away from open-source solutions such as MediaPipe Selfie Segmentation and choosing our SDK to get better quality, a broader set of effects, and ongoing technical support.
On the other side, companies migrating to platforms like the Zoom SDK may stop using a separate effects SDK because Zoom already provides a fairly robust built-in solution.
Our SDK may look complex because of the number of available features, but the actual integration is quite simple. On the web, for example, it usually takes only a few dozen lines of code. We also provide ready-to-use examples and integrations for platforms such as LiveKit, Cloudflare Meet, and the Zoom SDK.
How does performance hold up on lower-end mobile devices when running multiple effects like background blur and noise suppression at the same time?
Effects SDK
@eymenjez0 Thanks for the question! In our mobile SDKs, background segmentation runs on the GPU, while noise suppression runs on the CPU in a dedicated high-priority audio thread.
This separation helps distribute the workload more efficiently and makes performance much more stable, even when both features are running at the same