For a 24/7 YouTube stream, set the keyframe interval to two seconds and convert that duration into frames at the stream’s actual frame rate. That means 60 frames at 30 fps or 120 frames at 60 fps; YouTube also says not to exceed four seconds.
For H.264 encoded with libx264, FFmpeg can express a practical starting point with -g, -keyint_min and x264’s closed-GOP option. The fragments below illustrate encoder settings only: they are not complete streaming commands, and option support can differ between FFmpeg builds.
Choose the frame rate you will actually send
GOP length is often described as a frame count, but YouTube’s recommendation is expressed as a duration. The count depends on how many frames your output sends each second. If the output is 30 fps, a two-second interval spans 60 frames; if it is 60 fps, it spans 120.
Start with the frame rate you intend to deliver, not just the rate of the source file. For example, a 24 fps recording may be converted to 30 fps in the output pipeline. In that case, the GOP calculation should use the output’s 30 fps, because that is the stream YouTube receives. If you keep the output at 24 fps, use 48 frames instead.
Choose a rate the content and encoder can sustain consistently. A devotional video, a still-image ambience loop or a local-news playlist may not need the motion detail of 60 fps. Higher frame rates mean more frames to encode each second and may require more encoder capacity and upload bandwidth. These are separate considerations from GOP duration: do not increase or decrease the keyframe interval to compensate for a bitrate or processing problem.
YouTube’s live encoder settings guidance covers supported frame rates, protocols and other ingest settings. Keep the frame rate fixed when calculating the GOP if the stream is meant to run continuously. If you change it later, recalculate rather than reusing the old frame count.
Convert two seconds into frames
Use this straightforward calculation:
GOP frames = output frames per second × interval in seconds
For YouTube’s two-second target, multiply the output frame rate by two. The frame count is not a universal FFmpeg value: it is a way of representing the same duration at a particular rate.
| Output frame rate | Frames in two seconds | Practical GOP target |
|---|---|---|
| 24 fps | 48 | 48 frames |
| 25 fps | 50 | 50 frames |
| 30 fps | 60 | 60 frames |
| 60 fps | 120 | 120 frames |
YouTube Help gives 60 frames at 30 fps as an example of a two-second interval in its live-stream error guidance. The same arithmetic applies at other rates. If you use a fractional frame rate, consider how your encoder and output timestamping represent it; check the actual output rather than assuming a rounded label tells the whole story.
YouTube’s settings guidance recommends two seconds and says not to exceed four seconds. Treat that as a boundary, not as a suggestion to choose a longer interval for a 24/7 broadcast. A continuous schedule does not change the duration of an individual GOP. Long runtime creates separate operational concerns, such as monitoring and recovery after a disconnect.
Do not confuse GOP length with bitrate or total stream duration. A -g 60 setting does not mean 60 seconds, and a two-second GOP does not imply anything about how long the broadcast remains live. It controls the spacing of keyframes in the encoded video.
Use a closed GOP
A GOP, or group of pictures, is a sequence of video frames organised around keyframes. A keyframe can be decoded without relying on earlier pictures in the same way that dependent frames do. Closed-GOP behaviour keeps a group from depending on pictures outside its boundary, which matters to downstream processing and transcoding.
YouTube’s live error guidance says its pipeline requires a closed GOP for optimal transcoding. That is why the 30 fps illustration below includes -x264-params open-gop=0 for libx264. It requests closed-GOP behaviour from that encoder; it is not a generic option that can be assumed to work with every video encoder.
The other settings have related but distinct jobs. -g sets the maximum GOP size in frames for common FFmpeg encoders. -keyint_min constrains the minimum keyframe interval in encoders that support it. -sc_threshold 0 disables x264’s scene-change keyframe insertion, which can make spacing more regular when using x264. Together they are a practical way to aim for regular two-second spacing, not a command prescribed verbatim by YouTube.
There is a trade-off in suppressing scene-change insertion: an abrupt visual change will not trigger an extra keyframe through that mechanism. For a looping music or ambience channel, regular spacing may be a useful starting point. For content with rapid cuts, test the visual result and check the encoder documentation rather than assuming one setting suits every programme. The requirement to consider closed-GOP behaviour remains separate from this choice.
Illustrative FFmpeg settings at 30 fps
For a 30 fps H.264 output encoded with libx264, these video and audio options illustrate the two-second target:
-c:v libx264 \\
-g 60 -keyint_min 60 -sc_threshold 0 \\
-x264-params open-gop=0 \\
-c:a aac
The two occurrences of 60 refer to the 60-frame GOP target and minimum interval at 30 fps. The open-gop=0 parameter asks x264 for a closed GOP. The audio codec option is included only to show where an audio setting might sit; it does not configure audio bitrate, sample rate or the rest of the stream.
This is deliberately not a complete YouTube streaming command. It does not include an input, output protocol, destination URL or stream key, video bitrate, output frame-rate conversion, audio bitrate, or the other settings a real deployment needs. Do not paste it on its own and expect it to go live. The final command depends on the input, the chosen output encoder and protocol, and how you are managing credentials.
FFmpeg’s documentation describes GOP sizing and how options can be passed to encoders such as libx264. FFmpeg builds can be compiled with different encoders or versions, and the selected encoder may accept different options. Before using this fragment, check which encoder your installation provides and inspect its local help. If libx264 or an option is unavailable, do not assume that replacing the encoder name preserves the same behaviour.
Adjust the GOP for 60 fps
At 60 fps, the two-second calculation is 60 × 2 = 120 frames. If you use the same libx264 approach, the relevant illustrative settings become:
-c:v libx264 \\
-g 120 -keyint_min 120 -sc_threshold 0 \\
-x264-params open-gop=0 \\
-c:a aac
Use 120 for both GOP values because the target duration has not changed; the frame count has. Keeping the 30 fps values at 60 would produce a one-second interval at 60 fps, not the two-second interval you intended. Conversely, using 120 at 30 fps would make the interval four seconds, at YouTube’s stated ceiling rather than its recommended target.
A 60 fps output may be appropriate when the source has frequent motion and your encoder and connection can carry it reliably. If the source is a static image or a slow-moving playlist, 30 fps may be a more practical choice. Neither choice changes YouTube’s two-second duration recommendation. Decide the frame rate for the content and available capacity, then calculate the GOP from that rate.
Do not treat the table’s other rows as a list of YouTube-specific modes. They are conversions of the same duration. For instance, at 25 fps, 50 frames spans two seconds; if you later change the output to 30 fps, recalculate to 60. Where an output uses a non-integer rate or frame-rate conversion, validate the emitted stream and timestamps rather than relying only on the input file’s properties.
Add and verify the rest of the pipeline
Once the GOP target is clear, configure the complete ingest pipeline separately. YouTube lists RTMP and RTMPS as supported protocols, supports video codecs including H.264, H.265/HEVC and AV1, and recommends constant bitrate (CBR) in its live encoder settings. Those choices surround the GOP calculation; they do not change the frame-count arithmetic. Use the official guidance for current ingest requirements and make the command match the encoder and protocol you have chosen.
For a 24/7 playlist, establish a stable output frame rate and audio/video format before starting the long-running process. A noisy or inconsistent input can cause a stream issue that looks like an encoder problem, while an inadequate connection can interrupt delivery even when GOP settings are correct. If your stream uses a playlist, check that the files play in the intended order and that transitions do not introduce unexpected gaps; the guide to fixing FFmpeg playlist order in a YouTube loop stream covers that separate task.
Then verify three things rather than relying on the command text alone: the selected encoder accepted the options, the output is actually using the intended frame rate, and keyframes are appearing at roughly the intended interval with closed-GOP behaviour. Review FFmpeg’s startup and encoder logs, inspect the resulting stream with a suitable media-analysis tool, and watch YouTube Live Control Room for ingest warnings. Exact log wording and available inspection tools vary by build.
Make one controlled change at a time if the output differs from what you expect. If an option is rejected, consult the installed encoder’s help or the documentation for that encoder; an option written for libx264 may not map directly to another codec. If YouTube reports a keyframe interval or GOP issue, compare the observed interval with the output frame rate, then check the closed-GOP setting and actual encoder in use. Avoid changing bitrate or reconnect logic as a first response to a keyframe warning.
GOP configuration is not a restart or uptime plan. A process can be configured correctly and still stop because of a host failure, a network interruption or an input problem. YouTube’s encoder workflow describes the general process of connecting an encoder to a live stream. If you rely on FFmpeg running on your own machine, plan how it will be monitored and restarted after a failure. For a playlist workflow, setting up a continuous loop from a Linux server is a related operational guide; it does not replace checking your GOP settings.
For channels where the painful part is keeping a loop running after your own computer is switched off, StreamNeo turns an uploaded video into a YouTube live stream that runs from the cloud and is monitored and restarted if it drops. It is YouTube-only; it is not a substitute for choosing a valid frame rate, checking the stream key, or verifying ingest settings.
If you are planning a remote control workflow for a local setup, the article on OBS WebSocket settings for a YouTube loop stream may help with that separate control-plane task. Whichever approach you use, keep a record of the output frame rate and GOP target together. That makes it easier to diagnose a later change than trying to infer the original intent from a long command line.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
What GOP length should I use at 30 fps?
For YouTube’s recommended two-second interval, use 60 frames at 30 fps. With libx264, -g 60 is the main maximum-GOP setting in the illustration; the other options help aim for regular spacing and closed-GOP behaviour. Check that your actual output is 30 fps.
What GOP length should I use at 60 fps?
Use 120 frames for a two-second interval at 60 fps. Reusing 60 frames would make the interval one second at that output rate. The duration target stays the same when the frame rate changes; the frame count does not.
Is the FFmpeg fragment a complete YouTube command?
No. It only illustrates encoder settings and an audio codec choice. You still need to configure an input, output protocol and destination, stream key handling, bitrate, frame rate and the other settings required by your deployment, then verify the encoder accepted the options.
Does a 24/7 stream need a longer GOP?
No. A 24/7 schedule does not change the recommended interval: calculate two seconds at the stream’s output frame rate. YouTube says not to exceed four seconds, and its live guidance calls for a closed GOP for optimal transcoding; uptime and restart planning are separate operational concerns.