How to live stream a bird feeder or aquarium on YouTube

1. Choose the camera and the box that sends it

A live cam has three parts: the camera, something that turns its picture into a stream YouTube accepts, and an internet connection that never sleeps. There are three common ways to put them together.

For a stream that should run for months, we would pick the first. The camera already compresses its video to H.264, so the relay only copies it and adds sound. That is light work: an old laptop, a mini PC or a rented server can do it, and the camera can sit on a pole by the feeder with only a network cable or Wi-Fi to reach.

Before you start, live streaming has to be switched on for the channel. YouTube's getting-started page says you need to verify your channel and have had no live streaming restrictions in the past 90 days.

2. Set up the camera for YouTube

Most IP cameras have a main stream and a lower-quality sub stream. Use the main stream and set it in the camera's own settings page:

• Codec: H.264. YouTube's encoder spec also lists H.265 and AV1, but H.264 is the one that relays with the plain command below.
• Keyframe (I-frame) interval: 2 seconds. YouTube's spec says "Recommended 2 seconds" and "Do not exceed 4 seconds". On a camera at 25 fps that is an I-frame interval of 50.
• Constant bitrate if the camera offers it, since YouTube's spec asks for CBR.
• Bitrate: at least YouTube's minimum for your resolution, from the table below.

Those numbers decide most home setups. A bird feeder does not need 60 fps, and 720p or 1080p at 25 or 30 fps looks fine for birds and fish. Your upload speed needs headroom above the bitrate, and YouTube's advice is direct: "We recommend running a speed test to test your upload bitrate." Check your internet plan for a data cap, too; a month of 1080p is well over a terabyte.

3. Relay the camera to YouTube with ffmpeg

This command reads the camera's RTSP stream, copies the H.264 video as it is, adds a silent stereo track and sends both to YouTube's RTMP ingest. Replace the camera address and the stream key with yours (the address format differs by camera maker; it is in the camera's manual):

ffmpeg -rtsp_transport tcp -i "rtsp://user:password@192.168.1.50:554/stream1" \
  -f lavfi -i anullsrc=channel_layout=stereo:sample_rate=44100 \
  -map 0:v:0 -map 1:a:0 -c:v copy -c:a aac -b:a 128k -shortest \
  -f flv "rtmp://a.rtmp.youtube.com/live2/YOUR-STREAM-KEY"

• -rtsp_transport tcp asks the camera for RTSP over TCP, which copes better with Wi-Fi than the default UDP.
• -c:v copy sends the camera's video untouched, so the relay uses almost no CPU. It only works if the camera sends H.264.
• anullsrc makes the silent track. YouTube's encoder spec lists an audio codec ("AAC or MP3") and 128 Kbps for stereo, and a silent track keeps the stream in that shape when the camera has no microphone.
• If your camera has a microphone you want to use, swap -map 1:a:0 for -map 0:a:0 and drop the anullsrc line.

What we tested and what we did not: on October 28, 2026 we ran this command on our server with ffmpeg 7.0.2, with a 720p H.264 test clip (no audio) standing in for the camera, read in real time, and a local FLV file in place of YouTube. The output had the video copied as H.264 and a silent AAC stereo track at 44.1 kHz, as intended. We did not have a real camera or send to a real YouTube stream key, so test with your own camera before you leave it running. YouTube's own advice applies: "Tests should include audio and movement in the video similar to what you'll be doing in the stream."

A USB webcam cannot use -c:v copy in most cases, because the computer has to encode the picture. That is the case where OBS (below) is the easier tool.

4. Keep it running for weeks

The relay will stop sometimes: the camera reboots, the Wi-Fi drops, the router updates overnight. The fix is to start it again automatically. The simplest version is a shell script that restarts ffmpeg ten seconds after it exits:

#!/bin/bash
while true; do
  ffmpeg -rtsp_transport tcp -i "rtsp://user:password@192.168.1.50:554/stream1" \
    -f lavfi -i anullsrc=channel_layout=stereo:sample_rate=44100 \
    -map 0:v:0 -map 1:a:0 -c:v copy -c:a aac -b:a 128k -shortest \
    -f flv "rtmp://a.rtmp.youtube.com/live2/YOUR-STREAM-KEY"
  echo "$(date '+%F %T') ffmpeg stopped, restarting in 10 s"
  sleep 10
done

We tested the loop with the same test clip in place of the camera: each time the clip ended, ffmpeg exited and the script started it again ten seconds later. On a Linux box, a systemd service does the same job and also starts the relay after a reboot. Save the loop above as /usr/local/bin/feeder-cam.sh, make it executable, and add a unit like this (we did not install this one on our server):

[Unit]
Description=Bird feeder cam relay to YouTube
After=network-online.target
Wants=network-online.target

[Service]
ExecStart=/usr/local/bin/feeder-cam.sh
Restart=always
RestartSec=10

[Install]
WantedBy=multi-user.target

Beyond software, three things decide uptime:

• Power. A PoE camera (power over the network cable) and a small UPS on the router and relay box ride out short cuts. Set the computer's BIOS to power on after a power loss.
• Network. A cable beats Wi-Fi. If the camera must use Wi-Fi, put the access point close and give the camera a fixed IP address so the RTSP address never changes.
• Weather and heat. Outdoor cameras need a weatherproof rating and shade; an aquarium camera needs to be clear of splashes and lid condensation.

5. Or use OBS

OBS is the easier route if you want overlays, such as a species list, the local time or a donation link, or if your camera is a USB webcam. Add the camera as a Media Source, untick the local file option and paste the RTSP address as the input, or add a USB camera as a Video Capture Device. The cost is that OBS re-encodes everything, so the computer works harder, and OBS has no built-in restart if it crashes. For a plain view of a feeder, the ffmpeg relay is lighter.

6. The YouTube rules a 24/7 camera runs into

No full replay. YouTube's archive page says: "If your stream exceeds 12 hours, it may not be captured at all." A camera that streams for weeks will not leave a recording on the channel. YouTube's advice: "We recommend recording a local archive as a backup." Save the good moments, a hawk at the feeder or fry hatching, as clips while the stream is live or from a local recording. Our guide to live stream time limits explains the archive rule in detail.

Privacy. YouTube's privacy guidelines protect a person's image, which "refers to images, audio, video footage, or text that uniquely identify you", and contact info such as a home address. A feeder camera in a garden can pick up all of these: a neighbour's window, people walking past, a car's number plate, your house number, voices across the fence. Frame tight on the feeder or tank, check the shot in daylight and at night, and if your camera has a privacy mask setting, black out anything outside your own property. When someone complains about a recorded video, YouTube may let the creator "use the Trim or Blur tools in YouTube Studio to edit the video", but a live stream cannot be blurred after the fact, so the framing is your only real control.

Animals. Nature cams are well inside YouTube's rules, and the violent and graphic content policy says plainly: "We do allow content that shows animals fighting in the wild, like in a nature documentary." A predator taking a bird at the feeder is that kind of content. What the policy does not allow includes "Graphic content that features animals and intends to shock or disgust", so do not title or clip such a moment for shock, and never stage anything for the camera. On a fish tank, keep the tank healthy on camera; a stream of a neglected tank is not one you want to run.

The vertical feed. YouTube sends live streams in horizontal and vertical formats at once, and "The vertical stream is a center crop of the horizontal stream". Put the feeder or the busiest part of the tank in the middle of the frame so the vertical viewers see it too.

7. Night footage and sound

At night a bird feeder is empty, and most cameras switch to infrared, which shows the scene in black and white. That suits a garden with hedgehogs, foxes or owls. Two practical points: an IR camera behind a window sees its own lights reflected in the glass, so put it outside or turn IR off; and the camera's switch between day and night mode can briefly change the picture, which the relay passes on as it is. Fish tanks are the opposite problem: when the tank light goes off on its timer, the stream goes dark.

For sound, the choices are the camera's microphone, silence, or music. Real birdsong is the draw of many feeder streams, but the same microphone hears people talking, and voices count as personal information under YouTube's privacy rules. Music on a 24/7 stream has to be licensed for YouTube live; our guide to music licences for 24/7 streams compares the terms.

8. Off hours: loop a highlight reel instead

Some channels would rather not show a dark tank or an empty feeder all night. One option is to stop the live camera at dusk and run a looped highlight reel of the day's best visits until morning. That is a different kind of stream, a video file on repeat rather than a camera, and it should say so in the title or description, so viewers do not think they are watching live. Our 24/7 stream guide covers how looped streams work.

Before you go live

1. Live streaming is enabled and the channel is verified.
2. The camera sends H.264, a keyframe every 2 seconds, at or above YouTube's minimum bitrate.
3. Your upload speed has headroom over the bitrate, and your data cap covers a month of it.
4. The relay restarts on its own and starts after a reboot.
5. The frame shows no neighbours, passers-by, number plates or house numbers, by day and by night.
6. The microphone is off or cannot hear people, or the audio is licensed music or silence.
7. You record locally or clip highlights, because a 24/7 stream has no full replay.

FAQ