gitwtfhub

wtf is frigate-media-backup?

mattjgalloway/frigate-media-backup — explained in plain English

Analysis updated 2026-08-13 · repo last pushed 2026-06-22

PythonAudience · ops devopsComplexity · 2/5MaintainedSetup · moderate

TL;DR

A tool that automatically copies video clips and snapshots from your Frigate security camera system to offsite backup locations like cloud storage or a remote server, keeping your footage safe if the main system fails.

Mindmap

mindmap
  root((repo))
    What it does
      Backs up Frigate clips
      Listens for real-time alerts
      Tracks uploaded files
    Backup destinations
      Local hard drive
      Remote server
      Cloud storage
    How it runs
      Lightweight container
      Background service
      Retries failed transfers
    Use cases
      Home security footage
      Offsite archive of events
      Raspberry Pi camera setups
    Tech stack
      Python
      Container deployment
    Audience
      Self-hosted camera users
      Homeowners with cameras

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Back up motion-detected video clips from your Frigate security cameras to cloud storage automatically.

REASON 2

Archive security footage to a remote server so it survives if your local camera system fails or its disk fills up.

REASON 3

Keep a safe offsite copy of snapshots from detected events like a person walking up your driveway.

What's in the stack?

PythonDocker

How it stacks up

mattjgalloway/frigate-media-backup0verflowme/learnings0verflowme/r2ai
LanguagePythonPythonPython
Last pushed2026-06-222022-06-182025-11-19
MaintenanceMaintainedDormantQuiet
Setup difficultymoderateeasymoderate
Complexity2/51/53/5
Audienceops devopsresearcherdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · moderate Time to first run · 30min

Requires a running Frigate instance with MQTT enabled and a configured backup destination such as cloud storage or a remote server.

No license information is provided in the repository, so usage rights are unclear.

Wtf does this do

Frigate Media Backup automatically copies video clips and snapshots captured by Frigate, a popular open-source security camera system, to offsite storage. It sends every detected camera event to one or more backup destinations you choose, such as a local hard drive, a remote server, or cloud storage. This ensures your important security footage is safe even if the main Frigate system fails or the local disk fills up. The tool runs quietly in the background and listens for real-time alerts from Frigate. When Frigate notices something like a person walking up your driveway, it generates a clip and sends a message. This backup tool catches that message, fetches the video directly from Frigate's interface, and uploads it. It remembers what it has already uploaded by keeping a small local log, so if the system restarts, it will not waste time or bandwidth re-uploading the same files. This is ideal for homeowners running self-hosted security cameras who want to safely archive motion events. For example, if someone damages your mailbox, you want the footage preserved offsite rather than just sitting on a Raspberry Pi in your garage. It is designed to run continuously and handle network hiccups gracefully, retrying failed downloads or uploads so a temporary internet outage will not permanently drop a recorded event. The project is built to run as a lightweight container, making it easy to deploy on the same machine as your cameras or a separate server. It can back up snapshots too, but it turns that feature off by default because motion images can be very frequent and might quickly fill up your cloud storage. A notable tradeoff the project makes is prioritizing reliability and security over immediate speed. It streams large video files to temporary storage on disk rather than loading them entirely into memory, which prevents the system from crashing when handling large MP4 files. It also strongly encourages secure, encrypted connections to your camera server and warns against turning off security features.

Yoink these prompts

Prompt 1
Help me set up frigate-media-backup in a Docker container alongside my existing Frigate installation, including the MQTT connection settings and backup destination configuration.
Prompt 2
Write a docker-compose service for frigate-media-backup that backs up my Frigate clips to a remote server using SFTP, with snapshots disabled to save bandwidth.
Prompt 3
My frigate-media-backup container keeps failing to connect to Frigate. Help me troubleshoot the connection and verify my Frigate API URL and MQTT settings are correct.
Prompt 4
Configure frigate-media-backup to back up clips to my local NAS mount point and explain how the deduplication log prevents re-uploading files after a restart.

Frequently asked questions

wtf is frigate-media-backup?

A tool that automatically copies video clips and snapshots from your Frigate security camera system to offsite backup locations like cloud storage or a remote server, keeping your footage safe if the main system fails.

What language is frigate-media-backup written in?

Mainly Python. The stack also includes Python, Docker.

Is frigate-media-backup actively maintained?

Maintained — commit in last 6 months (last push 2026-06-22).

What license does frigate-media-backup use?

No license information is provided in the repository, so usage rights are unclear.

How hard is frigate-media-backup to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is frigate-media-backup for?

Mainly ops devops.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.