For a 24/7 YouTube radio stream with a static image, begin with YouTube’s general live encoder guidance: use RTMP or RTMPS, a supported video and audio codec, constant bitrate (CBR), and a two-second keyframe interval. Choose a resolution and bitrate your upload connection can sustain reliably; YouTube does not publish a separate bitrate profile for a still image.
A sensible first test is often 720p at 30 fps, using the bitrate recommended for your chosen codec as a reference rather than a guarantee. Check the incoming preview, listen for uninterrupted audio, and watch YouTube’s stream-health messages before relying on a setup overnight.
Recommended starting settings for a static-image radio stream
Think of the stream as an audio programme carried inside a live video feed. The image may stay still, but YouTube still receives video frames, and its published recommendations cover live encoders generally rather than radio streams with a still graphic. The following choices are a practical starting point, not a special YouTube preset.
| Setting | A reasonable first test | What to keep in mind |
|---|---|---|
| Ingest protocol | RTMPS where your workflow supports it | YouTube recommends RTMPS; RTMP is also listed. |
| Video codec | H.264 if your encoder supports it | AV1 and H.265/HEVC are also listed by YouTube. Use a codec your encoder and workflow handle correctly. |
| Resolution and frame rate | 720p at 30 fps | A modest frame rate suits an unchanged image, but YouTube does not prescribe a radio-specific rate. |
| Video bitrate mode | CBR | Use the matching YouTube bitrate recommendation as a reference, then test your actual connection. |
| Keyframe interval | Two seconds | YouTube recommends this frequency and says not to exceed four seconds. |
| Audio | AAC or MP3; stereo settings described below | Listen to a test, not only the encoder’s status panel. |
| SDR colour | Rec. 709, 8-bit | Relevant to the video feed even when its content is a still image. |
For example, a creator whose encoder supports H.264 could test 720p30 against YouTube’s 8 Mbps recommendation, then check that the connection and outgoing feed remain stable under the conditions in which the channel will run. That figure is the published video ingestion recommendation, not a promise that an internet connection, encoder or service will perform reliably at it. You may have reasons to test another resolution or codec; compare the published figures later in this article.
Do not choose settings from a speed test alone. A connection can show a high upload speed at one moment and still vary later, or be shared with other devices. Leave practical headroom, avoid heavy competing uploads during a test, and see whether YouTube reports health problems while representative audio is playing.
If you are deciding between a computer-based setup and a cloud workflow, the difference is mainly operational: a local encoder depends on the computer and connection staying available, while a cloud workflow can run without your computer being switched on. For an example of planning a scheduled file-based broadcast, see how to schedule prerecorded videos for YouTube livestreaming. Whatever workflow you choose, YouTube’s ingest settings and your content rights still matter.
YouTube’s general live encoder requirements
YouTube’s live encoder settings are the baseline for an encoder-based broadcast. The page lists RTMP and RTMPS for ingestion, H.264, H.265/HEVC and AV1 video, and AAC or MP3 audio. It recommends CBR and a two-second keyframe frequency, with keyframes not exceeding four seconds. These settings describe the encoder’s feed to YouTube, not a guarantee of what viewers will receive on every device or connection.
A stream key connects your encoder to the broadcast you created in YouTube Studio. Treat it as a password: anyone who obtains it may be able to send a feed to your channel. YouTube’s stream setup guidance explains where the key and stream URL fit into the workflow. Copy them carefully, keep them out of public screenshots and reset the key if you believe it has been exposed.
In YouTube Studio, create or schedule a live stream, set its title and visibility, and then use the Live Control Room to connect the encoder. Before making the stream public, check the preview and confirm that the image is framed correctly and the audio is arriving. Private or unlisted testing can help you inspect the feed without presenting it as a public programme; choose visibility deliberately for the audience you intend to serve.
YouTube says automatic detection of resolution and frame rate is the default recommendation. If you need manual control, YouTube notes that you can use a custom stream key. The practical choice depends on your encoder: a controlled, fixed output can make troubleshooting easier, while automatic detection avoids some manual configuration. Avoid changing several settings at once, since it becomes harder to identify the cause if the preview fails or health messages worsen.
H.264 and AV1/H.265 bitrate examples
YouTube publishes different recommended video bitrates by codec, resolution and frame rate. The figures below are from its encoder guidance and are ingestion recommendations. They are not measured results from this article and do not mean that one figure will work on every connection.
| Ingest resolution and frame rate | H.264 video bitrate | AV1 or H.265/HEVC video bitrate |
|---|---|---|
| 720p30 | 8 Mbps | 6 Mbps |
| 1080p30 | 14 Mbps | 10 Mbps |
| 720p60 | 8 Mbps | 6 Mbps |
| 1080p60 | 17 Mbps | 12 Mbps |
The 720p30 figures make a useful comparison for a simple radio visual: YouTube’s table lists 8 Mbps for H.264 and 6 Mbps for AV1 or H.265 at that size and frame rate. At 1080p30, the listed recommendations are 14 Mbps and 10 Mbps respectively. Do not read the lower number as proof that a newer or less familiar codec is automatically the right choice for your whole workflow. Your encoder must support it, and the video must be encoded and sent correctly.
The table is about the video bitrate. Keep audio configuration in view as a separate part of the outgoing feed, and account for the full stream when considering the capacity and consistency of your upload connection. YouTube automatically transcodes an incoming stream into multiple output formats, but that does not remove the need to send a healthy feed to YouTube in the first place.
H.264 is a common, straightforward starting choice when compatibility with an existing encoder matters. AV1 or H.265 may be appropriate when supported by your tools and workflow; consult your encoder’s own documentation and test the result. A codec label alone cannot tell you whether the encoder is configured correctly, whether the image looks as intended, or whether the upload path is stable. For a wider view of equipment choices, this guide to what you need to go live can help you think through the rest of the setup.
Choose resolution and bitrate for your connection
A static image can make a lower frame rate a sensible practical choice, because there is no camera movement to represent. It does not eliminate the video feed, nor does it create an official discounted bitrate target. Choose a resolution that suits the artwork and the connection you can test, then use YouTube’s matching codec and frame-rate row as a starting reference.
For a channel whose artwork is a logo, album cover or simple background, 720p30 may be enough for the viewing experience you want. If small text or detail needs to remain legible, test whether 1080p30 makes a visible difference on a phone and a larger screen. Higher resolution is not automatically better if it creates a feed that your connection cannot sustain. Conversely, do not assume the lowest available setting is suitable without checking that the graphic remains readable.
Start with the official recommendation for the exact codec, resolution and frame rate selected. Run an upload speed test, preferably under ordinary household or business network conditions, and allow headroom for variation and other network use. A speed test is a snapshot rather than a night-long guarantee. If the connection is shared, repeat the test when other routine activity is present; a quiet test window can conceal contention that appears later.
When the health indicator reports instability, simplify the test in a controlled way. Try the lower resolution or a codec supported more reliably by your encoder, then repeat the same audio and monitoring procedure. Keep a note of each combination, the observed health messages and the time period tested. That record is more useful than changing resolution, bitrate, codec and network arrangements simultaneously and then guessing which adjustment helped.
If you are comparing a local computer with a managed or cloud approach, include the power and connection that the local machine needs, not just the encoder settings. Readers planning an always-on music channel may also find it useful to see how a 24/7 Malayalam songs stream is approached. The content format differs, but the practical questions about a continuous feed, a test and a stable workflow overlap.
Configure audio and keyframes
For a radio stream, a healthy video preview is not enough. Confirm that audio is present, at an appropriate level and continuous, with no unintended silence, clipping or abrupt changes at loop boundaries. YouTube lists AAC or MP3 as audio codecs and gives 128 kbps for stereo audio as its recommended advanced setting. Its guidance also lists a 44.1 kHz stereo sample rate. These are useful reference settings; check what your encoder actually sends and listen from the viewer side.
A two-second keyframe interval is YouTube’s recommended frequency, and the interval should not exceed four seconds. Set it in the encoder if you are configuring the feed manually. A static visual does not change this instruction: the recommendation concerns the structure of the video stream, not how often the artwork itself changes. If the encoder presents a setting in frames rather than seconds, use its documentation to translate the intended interval for the selected frame rate rather than guessing.
Use CBR for the video bitrate mode as YouTube recommends. Confirm that the encoder is sending the intended resolution, frame rate, audio codec and sample rate; the preview and stream-health panel are more useful than assuming a saved preset reflects the output. For SDR, YouTube lists Rec. 709 and 8-bit colour. A graphic with fine text or gradients is a good test image because it can reveal cropping, unexpected colour or compression artefacts more clearly than a plain background.
If the radio programme is assembled from tracks or a playlist, test the transition points as well as an ordinary section. A short sample that begins in the middle of one track may miss a long silent gap or a clipped loop boundary. Make a test that includes the start, an ordinary transition and the kind of quiet passage that will occur during the actual broadcast.
Test with representative audio and monitor stream health
YouTube recommends testing with audio and movement similar to the planned stream, then checking stream health. For a radio channel, that means using the actual audio chain and representative programme material rather than a silent test screen. Although the image is static, audio level, track changes, processing and file transitions can all expose problems that a few seconds of setup will not reveal.
Before going live, inspect the preview in the Live Control Room. Check that the correct artwork is visible, not stretched or cut off, and verify that the audio is audible on a separate playback device if possible. Watch for audio/video warnings and other health messages. The YouTube live streaming operations guide describes monitoring during a broadcast; follow the current messages shown for your stream rather than treating a successful connection as proof that all is well.
During a longer test, listen at more than one point. Confirm the start of the stream, at least one change between programme items, and a later section after the encoder has been running. If you cannot listen continuously, arrange a check at a time when someone can respond to a warning or interruption. A dashboard can report a healthy incoming feed while an audio problem remains obvious to a listener, so use both the status information and actual playback.
For an always-on workflow, also decide who will notice if the feed stops and what they can do. YouTube’s monitoring messages can help identify ingestion problems, but no encoder setting promises uninterrupted operation. Keep access to the encoder and stream key controlled, and document how to check the feed and recover it. StreamNeo can remove the need to keep your own computer running for an uploaded file-based broadcast, while still leaving you responsible for checking the channel, content and rights.
Why a static image does not create a special profile
YouTube’s published encoder guidance gives general recommendations for live ingestion; it does not publish a special profile for a 24/7 radio stream with a static image. The table’s bitrate values vary by codec, resolution and frame rate. They are not replaced by an official lower target merely because the picture does not move.
A still image may be less visually complex than a camera scene, and a low frame rate may be a practical fit for it. Those observations can inform what you test, but they do not establish a guaranteed reduction in bitrate. The image still has to be encoded into a video feed, and the audio continues to be part of the broadcast. Base the configuration on YouTube’s general values, your encoder’s capabilities and the results of a real test.
Separate the technical question from the content question. A stream can meet the encoder recommendations and still be interrupted for reasons unrelated to resolution or bitrate. YouTube scans live streams for third-party content, and its copyright guidance for live streams explains that detected content can lead to replacement, interruption or termination. A static image does not change the rights needed for music.
Check that the music rights cover the planned live use, relevant territories and any archive you intend to keep. YouTube notes that even licensed third-party content can be interrupted if the rights owner has not allowlisted your channel through Content ID. Confirm any allowlisting requirement with the rights owner; do not assume that a licence or a still visual settles the question. The technical guide to running a 24/7 reggae instrumental radio stream addresses a related continuous-music use case, but you must verify the terms for your own catalogue and use.
Plan separately for the replay. YouTube warns that streams longer than 12 hours may not be captured at all and recommends keeping a local recording if a complete copy matters. A long continuous live session should not be treated as a guaranteed complete archive. If distinct replay files matter, consider planned session boundaries and test the actual archive behaviour; the idea of stopping and restarting on a schedule is a practical response to YouTube’s warning, not a promise about how any individual stream will be saved.
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 bitrate should I use for a 24/7 radio stream with a still image?
There is no special bitrate published for that use case. Use YouTube’s recommendation for your codec, resolution and frame rate as a reference; for example, its 720p30 table lists 8 Mbps for H.264 and 6 Mbps for AV1 or H.265. Test the feed on the upload connection you intend to use, because neither figure guarantees that every connection will be stable.
Does a static image let me use less bitrate?
A still image may be less visually complex, and a lower frame rate may be a reasonable practical choice, but YouTube does not publish a reduced static-image target. The feed still includes video and audio, so test the intended output and inspect stream health rather than assuming that a low bitrate will work.
Will a 24-hour stream always be saved as a replay?
No. YouTube says streams longer than 12 hours may not be captured at all, so do not promise a complete replay from one continuous session. Keep a local recording if you need a complete copy, and test any planned session boundaries against your archive needs.
Can a still image prevent a music-rights interruption?
No. The image does not alter the rights required for music in a live stream or archive. Confirm the rights for your use and ask the rights owner whether channel allowlisting through Content ID is required; licensed material can still be interrupted if the channel is not allowlisted.