Home / Guides

Frigate Camera Requirements: RTSP, ONVIF, Substreams & Codecs

Frigate camera requirements explained: stable RTSP, usable substreams, compatible codecs, local credentials and where ONVIF helps.

Updated September 23, 2026 · SecurityVerdicts research desk

Frigate does not need a camera with expensive cloud AI. It needs a stable video source that your local server can decode reliably. In practice, clean RTSP access and a usable low-resolution substream are often more valuable than proprietary smart features.

Main stream and detect stream

Frigate supports separate inputs for recording and detection. That lets you record a high-resolution stream while object detection runs against a smaller stream, reducing decode and inference overhead.

Protocol priorities

Feature	Why it matters
RTSP	Common direct stream path for FFmpeg/go2rtc.
Substream	Reduces detection decode load.
ONVIF	Useful for discovery/events on compatible setups, though not required for basic RTSP ingest.
Local account	Avoids cloud-only authentication in the recording path.
PoE	Improves power/network reliability for fixed cameras.

Codec configuration matters

Frigate documentation recommends H.264 for broad live-view compatibility and notes that keyframe interval should generally match frame rate. Non-standard “smart codec” modes can create playback problems.

Architecture rule: let the camera produce stable video and let Frigate do the local AI. Do not pay twice for overlapping cloud intelligence unless you actually need the vendor service.

2026 Frigate camera setup checklist

Current Frigate guidance favors configuring the camera itself for the resolution and frame rate you actually want instead of decoding unnecessary frames and discarding them later. For a normal installation, use a high-quality stream for recording and a lighter stream for detection when the camera exposes both.

Setting	Practical starting point	Why
Detect stream	Lower-resolution substream	Reduces decode and inference load while preserving the main stream for evidence.
Detect frame rate	About 5 fps for most scenes	Frigate identifies 5 fps as the normal default for most cameras; increase only when the scene genuinely requires it.
Video codec	H.264 when available	Broadest compatibility across Frigate live view and browsers.
Audio codec	AAC when audio is needed	Best general compatibility for recording and playback.
I-frame interval	Match the stream frame rate	Shorter, predictable keyframe timing improves stream startup and recovery.
ONVIF	Helpful, not mandatory	Useful for discovery, profiles and some events; a manually configured RTSP stream can still work without ONVIF.

Use the camera wizard before hand-writing configuration

Frigate's current Camera Management wizard can probe supported cameras over ONVIF, test available streams, assign separate detect and record roles, validate codecs and resolutions, and create the initial configuration. Manual RTSP remains useful when ONVIF discovery is unavailable or a vendor needs a model-specific stream path.

Reolink needs model-specific attention

Frigate's current camera-specific documentation notes that Reolink behavior varies by generation and resolution. Older 6MP+ RLC-8xx cameras generally use RTSP, while newer models can have different recommended stream paths. For supported Reolink models, Frigate also recommends constant-bit-rate behavior when available and an interframe setting of 1×.

Fast buying rule: prioritize a camera with a stable local stream, a usable substream, controllable codec/frame-rate settings and reliable continuous power. Treat vendor cloud AI as optional because Frigate supplies the local detection layer.

Official references: Frigate camera setup · camera configuration · camera-specific guidance. Then compare our Frigate camera shortlist.