Reolink 4K Camera Setup for Frigate: Local Storage, No Cloud, Full Control

Reolink cameras are built for self-hosted setups. They ship with firmware that plays nicely with Frigate, they support PoE power, and they don’t nag you for cloud subscriptions. Setting up a Reolink 4K camera with Frigate is straightforward if you understand the core steps: wiring, network discovery, stream configuration, and Frigate integration.

This guide walks you through a working setup from the ground up.

What You Need Before You Start

Hardware:

Reolink 4K PoE camera (we’ll cover model choices below)
PoE injector or PoE switch (802.3af or 802.3at depending on camera power draw)
Cat6/Cat6a cabling rated for outdoor use if running runs over 100m
Frigate NVR instance (VM, bare metal, or Docker container)
Network with a static IP subnet for cameras

Knowledge:

Basic networking (DHCP, static IPs, subnet masks)
Docker or familiarity with your Frigate deployment method
Ability to SSH into your NVR and edit YAML config files

Don’t overthink it. Reolink cameras are designed for this workflow.

Step 1: Physical Installation & PoE Wiring

Run your PoE cable from your switch or injector to the camera location. Reolink 4K models typically draw 30–50W depending on the model, so confirm your PoE source can supply adequate power. A standard 802.3at (30W) injector is usually sufficient, but check your specific camera’s datasheet.

Once the cable is in place and the camera powers on, you’ll see a status LED. Give it 30–60 seconds to boot and pull an IP from your DHCP server. If you’re running a dedicated camera subnet (recommended for Frigate setups), ensure your PoE switch or injector is on that same VLAN.

Step 2: Find Your Camera’s IP and Access the Web UI

Log into your router or use a tool like nmap or arp-scan to find the camera’s IP:

arp-scan -l | grep -i reolink

Once you have the IP, open a browser and go to http://<camera-ip>. Log in with the default credentials (usually admin / 12345). Change this password immediately—even in a local-only setup, it’s good practice.

Step 3: Configure Camera Network Settings

In the web UI, navigate to Settings > Network.

Set a static IP for the camera. Don’t rely on DHCP; IP churn breaks Frigate.
Enable ONVIF (found under Settings > Network > ONVIF). This is optional but recommended for discovery and compatibility.
Note the RTSP stream URLs. Reolink cameras expose streams like:
- rtsp://<user>:<password>@<ip>:554/h264/ch1/main/av_stream (main stream)
- rtsp://<user>:<password>@<ip>:554/h264/ch1/sub/av_stream (substream)

Save your credentials. You’ll need them for Frigate config.

Step 4: Add the Camera to Frigate

Edit your Frigate config.yml:

cameras: reolink_4k_front: ffmpeg: inputs: - path: rtsp://admin:[email protected]:554/h264/ch1/main/av_stream roles: - detect - record detect: width: 1920 height: 1080 objects: track: - person - car

Use the main stream for detection and recording. If your Frigate instance is CPU-constrained, use the substream for detection and main stream for recording.

Restart Frigate. Within 30 seconds, you should see the camera in the Frigate UI with live video.

Step 5: Optimize for 4K Recording (Optional)

Reolink 4K models can record at 2560×1920 or higher, but Frigate’s object detection doesn’t need that resolution. A practical approach:

Detection stream: Resize to 1920×1080 or lower (saves CPU)
Recording stream: Keep native 4K resolution for archival

In your config, use separate inputs:

cameras:
  reolink_4k:
    ffmpeg:
      inputs:
        - path: rtsp://admin:[email protected]:554/h264/ch1/main/av_stream
          roles:
            - record
        - path: rtsp://admin:[email protected]:554/h264/ch1/sub/av_stream
          roles:
            - detect
    detect:
      width: 1920
      height: 1080

This splits the load: substream handles AI detection, main stream handles storage.

Recommended Reolink 4K Models for Frigate

The best budget PoE camera for Frigate article covers entry-level options in depth. For 4K specifically:

Reolink RLC-823A — 4MP dual-lens (turret), solid low-light, PoE, under $110. Great starting point.
Reolink RLC-810A — 4MP bullet, clean design, reliable RTSP. Widely used in Frigate communities.

Both ship with RTSP enabled and no cloud requirement. If you’re building a multi-camera setup, also review our PoE camera no subscription 2026 guide for comparison with other brands.

Storage & Retention

4K or high-bitrate streams consume 50–150 GB per camera per week, depending on motion and compression. Plan your NVR storage accordingly:

SSD pool: Fast playback and scrubbing in Frigate UI
HDD array: Cost-effective long-term storage (RAID 5 or 6 recommended)

Set Frigate retention policies in config.yml:

record:
  retain:
    days: 30
    mode: motion

Motion-only retention cuts storage by 60–70% for low-activity zones.

FAQ

Q: Can I use Reolink cameras without PoE? Some Reolink models (like the Reolink E1 Outdoor) use WiFi or proprietary power. These work with Frigate via RTSP, but PoE is preferred for reliability and zero cloud dependency. Check your model specs.

Q: Do Reolink cameras require a Reolink hub or NVR? No. Reolink cameras output RTSP streams that Frigate consumes directly. You don’t need Reolink’s own NVR, though their hub can serve as a backup power/network failover device if you want extra redundancy.

Q: What bitrate should I use for 4K recording in Frigate? Reolink 4K cameras typically output 4–8 Mbps at main stream. Let Frigate record whatever the camera sends; your disk will tell you if it’s too much. Monitor disk write speed to avoid bottlenecks on large setups (10+ cameras).