Resources: FAQs

Video APIs are great, but relatively simple, pieces of technology. They take a user's upload, encode it with H.264, store it somewhere like S3, and deliver it to viewers via HLS and a CDN. They do that for any video file they're given. They have nothing to do with the video's actual content. But what if that video contains nudity, graphic violence, or hate

How E2EE video calls work in practice, from device authentication and group keys to SFrame frame encryption, SFU forwarding, and rekeying when people join or leave.

Discover how AI image moderation filters work. Covers how they hash, classify, and OCR every image, then how per-category thresholds decide what to allow, flag, or block, and where the models still get it wrong.

How simulcast lets one video call serve every viewer's bandwidth, what it costs the sender, and how it differs from SVC, transcoding, and multistreaming.

How WebRTC gets two devices behind different routers to connect, covering NAT, STUN, signaling, ICE hole punching, TURN relays, and the RTCPeerConnection API.

Choppy call audio is usually jitter, not bandwidth. See how a jitter buffer reorders and paces packets, how it picks its size, and how it conceals lost packets.

Frame rate controls one specific property of video, how densely motion gets sampled over time, and most decisions around it get easier once you know which one. This covers what frame rate measures, how it differs from resolution and bitrate, how to pick a rate, and the bugs that come from treating fps as one uniform number.

Echo happens because every device on a call plays and records audio at once, and the delay added by network transit and buffering is what makes the overlap audible instead of unnoticeable. This covers how acoustic echo cancellation works, WebRTC's default AEC3 pipeline, why users still hear echo, and how to fix it.