For a 1080p slideshow stream, start by choosing the frame rate and codec, then use the matching row in YouTube’s general live bitrate recommendations as a reference. YouTube does not publish a separate bitrate table for still-image slideshows, and a recommended rate does not mean your upload connection can sustain it.
For many slide sequences, 1080p at 30 fps is a sensible place to begin; use 60 fps only if the material or transitions benefit from it. Check the capacity of the connection you will actually use, leave headroom, and test the full sequence—including audio—before relying on it overnight.
Choose resolution and frame rate for the slides
Start with the images and the way people will watch them. If your source artwork is 1920 by 1080 pixels, a 1080p output can preserve its detail without requiring you to enlarge the images. If most source images are smaller, or the connection is constrained, 720p may be a more practical output. The important point is to choose intentionally: sending a larger frame does not create detail that is absent from the original images.
A static slide does not need 60 frames per second merely because the encoder offers it. At 30 fps, the output still refreshes at a standard video frame rate, while a dissolve or pan can provide the motion viewers see between slides. If your sequence has smooth movement, such as animated backgrounds or frequent transitions, compare the result at 30 and 60 fps in a private test. The higher frame rate changes the applicable bitrate recommendation and may add load to the encoder and connection.
YouTube’s settings depend on the incoming resolution, frame rate and codec. The creator sets these in the encoder; YouTube says it detects the incoming settings and transcodes the stream for different devices and network conditions. That does not remove the need to send a stable feed. Choose an output that matches your content and your equipment, rather than assuming YouTube will correct an unstable source.
If you are assembling a devotional sequence, first decide whether each image should remain still for a long time or whether you want gentle changes between them. The Krishna bhajan OBS setup guide may help with the broader source-and-scene workflow; bitrate selection still needs to be matched to your own encoder and upload. For a channel that stays live continuously, the Gurbani stream guide covers the wider 24/7 context, while this page concentrates on image output and bitrate.
Use YouTube’s H.264 recommendations as a reference
For an H.264 stream, YouTube’s general recommended ingestion rate at 1080p30 is 14 Mbps. At 1080p60 it is 17 Mbps. These are not slideshow-specific targets. YouTube’s table also lists minimum rates—5 Mbps for 1080p30 and 6 Mbps for 1080p60—but treating a minimum as a reliable operating target would be unwise without a test under your own conditions.
At 720p, YouTube lists 8 Mbps recommended for both 30 and 60 fps H.264. This can make 720p worth testing when the source material is modest or the upload connection cannot comfortably accommodate a higher target. It is not a promise that a particular connection will carry the stream successfully, and it is not a reason to pick 720p if important text in your slides becomes difficult to read.
| Output choice | H.264 minimum listed by YouTube | H.264 recommended by YouTube | Practical reading for a slideshow |
|---|---|---|---|
| 1080p at 30 fps | 5 Mbps | 14 Mbps | A useful first comparison for still slides and ordinary transitions; check capacity before using the recommendation. |
| 1080p at 60 fps | 6 Mbps | 17 Mbps | Consider when visible movement benefits from a higher frame rate; not necessary just because slides are static. |
| 720p at 30 fps | 3 Mbps | 8 Mbps | A lower-resolution alternative to test when it preserves legible text and fits the available connection better. |
| 720p at 60 fps | 3 Mbps | 8 Mbps | The same listed rate as 720p30, but the extra frame rate may not benefit a mostly still sequence. |
The values are YouTube’s general guidance for live encoder ingestion, not a prediction of visual quality for your particular set of slides. A mostly static frame can look acceptable at a lower rate than a fast-moving scene, but bitrate is not the only factor: image detail, text, fades, compression behaviour and the encoder all affect the output. Do not lower the rate solely because a slideshow appears simple; make a test and inspect the result on the devices your audience uses.
YouTube recommends constant bitrate encoding and a keyframe interval of two seconds, with intervals not exceeding four seconds. Where your software exposes these controls, set them to match the guidance and confirm the encoder is sending the selected codec, frame size and frame rate. The current official reference is YouTube’s encoder settings and bitrate guidance. Recheck it before a later setup, since published guidance can change.
Compare AV1 and HEVC recommendations
YouTube groups AV1 and H.265/HEVC together in its recommended-rate table. At 1080p30, the recommended value is 10 Mbps, and at 1080p60 it is 12 Mbps. The listed minima are 4 Mbps for both 1080p frame rates. At 720p30 and 720p60, YouTube lists 6 Mbps recommended and 2 Mbps minimum for this codec group.
These figures are useful only if your encoder can send the codec you select and the receiving workflow accepts it. Do not switch codecs based on the rate table alone. Check the encoder’s available options, its documentation and the settings accepted by YouTube for your stream. An available software encoder may be sufficient; YouTube describes encoders as software applications or standalone hardware, so buying a separate device is not a prerequisite for a documented OBS slideshow workflow.
The table below summarises the relevant published values. Use the row that actually matches the codec and output you intend to send; do not mix an AV1 recommendation with an H.264 stream.
| Output choice | AV1 or H.265 minimum listed by YouTube | AV1 or H.265 recommended by YouTube |
|---|---|---|
| 1080p at 30 fps | 4 Mbps | 10 Mbps |
| 1080p at 60 fps | 4 Mbps | 12 Mbps |
| 720p at 30 fps | 2 Mbps | 6 Mbps |
| 720p at 60 fps | 2 Mbps | 6 Mbps |
The lower recommended figures do not mean that AV1 or HEVC is automatically a better choice for your channel. Codec support, compatibility and the ability to encode reliably matter alongside the nominal bitrate. If you already have a working H.264 workflow, compare an alternative only in a controlled test, changing one setting at a time so you can tell whether the difference comes from codec, resolution, frame rate or connection conditions.
Set a sustainable upload target
A bitrate from YouTube’s table is a reference, not a capacity guarantee. Your stream’s total bitrate cannot exceed the upload bandwidth available, and YouTube recommends keeping 20% headroom. For example, if the encoder is set to send video at a published recommendation, the connection still needs room for audio and other network traffic, as well as a margin for variation. If sending primary and backup streams, include both in the capacity calculation.
Check outbound upload capacity on the same connection and, as far as possible, under the conditions in which the channel will run. A one-off speed test on an idle network may not represent evenings when household devices are active. Consider whether other people are using the connection, whether the computer is on Wi-Fi, and whether the route to the router or network provider is prone to interruptions. A test result is evidence about that moment, not a promise about the next night.
Use the following process to choose a target:
- Select a resolution, frame rate and codec based on the slides and encoder support.
- Look up the matching YouTube row and note both the minimum and recommended rate.
- Check stable outbound capacity and retain the recommended headroom beyond the total stream bitrate.
- If the recommendation leaves too little margin, test a lower output resolution or a different supported codec rather than assuming the connection will hold.
- Repeat the test while other expected network use is present, and monitor the actual YouTube stream health messages.
The YouTube streaming tips page explains the bandwidth and headroom consideration. If you need to think beyond the encoder itself—such as what happens when the home connection drops—the restart-after-internet-loss guide looks at that separate continuity problem. A sustainable bitrate cannot prevent an internet outage, and recovery behaviour cannot make an overloaded connection stable.
There is also a practical distinction between the encoder’s configured bitrate and the stream’s total use. Audio adds data, and a backup feed, if you use one, adds more. Keep the calculation on the conservative side and leave room for routine variation rather than setting the video rate right up against a speed-test result. If the channel must continue while your own computer is off, the operating arrangement matters too: once you have settled the file and settings, StreamNeo removes the need to leave a local computer running for the broadcast, which is useful when a home machine or connection is the specific source of overnight interruptions.
Configure the slideshow to repeat
For still-image files in OBS, use the Image Slide Show source. It accepts individual images or directories and provides automatic or manual slide modes, transition choices, timing, looping and randomised playback. Decide whether your images should appear in a fixed sequence—useful for a service order, lesson or announcement—or shuffle between sessions. Turn on Loop if the sequence should begin again after its final image.
OBS documents defaults of Fade for the transition, 8,000 milliseconds between slides, 700 milliseconds for transition speed, and looping enabled. Treat these as starting defaults, not ideal timings for every channel. A bhajan image with lyrics may need more reading time than a short title card; a local news slide may need a deliberate dwell time so viewers can absorb the information. Open the source properties and verify the actual timing rather than relying on what you remember from a previous scene.
If the playlist is made up of video or audio media rather than still images, OBS’s VLC Video source is the relevant path. It offers playlist loop and shuffle controls, and VLC must be installed for that source to be available. That is a different source type from Image Slide Show: use it for media files, not as a substitute for per-image transitions. For more on a continuous prerecorded video path, see the guide to looping videos on YouTube Live with Raspberry Pi and FFmpeg.
Before leaving a loop unattended, let it reach the last item and return to the first. Check the seam: does the transition complete cleanly, does a blank frame appear, and does audio stop or restart abruptly if there is a soundtrack? Ordered playback can make a scheduled sequence predictable; shuffle can keep a long station from repeating the same order every cycle, but may be unsuitable when slides must appear in a specific sequence. Choose the behaviour your audience needs, then test it end to end.
Test transitions, audio and stream health
A bitrate test that shows a still frame is not enough if the broadcast includes transitions. Fades, animated overlays, moving backgrounds and changes in image detail can affect the encoded signal. Test with the real sequence, including the busiest transition or most detailed slide. Include the actual audio if you plan to use it, and listen for clipping, silence, an unexpected restart or a mismatch between the picture and soundtrack.
YouTube’s own guidance is to test before going live and to make the test resemble the intended event, including audio and movement. In Live Control Room, review stream health and any messages before treating the setup as ready. During an initial broadcast, keep an eye on health rather than assuming that a successful connection at the start will remain healthy. The OBS settings guide for a 24/7 ambient music stream can help with adjacent continuous-stream considerations, though your final settings should follow the source material and the YouTube row you selected.
A useful test is repeatable. Record the selected resolution, frame rate, codec, bitrate and keyframe interval; note the connection used and whether other devices were active. Watch the stream output rather than only the local preview, because the encoded and received result is what viewers will see. If you change a setting, test again. Changing several at once makes it harder to identify whether a problem came from bitrate, the image sequence, audio, encoder load or network capacity.
Look for practical signs rather than relying on a single number: buffering or health warnings, dropped frames, a soft or blocky image during a transition, unreadable small text, audio interruptions, or a loop that stalls at the end. If a test fails, reduce the demand in a deliberate order: try 30 rather than 60 fps if the motion allows it, test 720p if it remains legible, or choose a codec your encoder handles reliably. Then repeat the stream-health check. No bitrate setting eliminates the need to monitor a real broadcast.
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 YouTube slideshow stream?
There is no separate YouTube bitrate table for slideshows. For a starting comparison at 1080p30, YouTube’s general recommended rates are 14 Mbps for H.264 and 10 Mbps for AV1 or H.265; choose the matching codec row and check that your upload has room for the total stream bitrate plus headroom. Test the actual slides and transitions before settling on a setting.
Does a slideshow need less bitrate than ordinary video?
Still images may contain less movement than many video scenes, but that does not establish a universal lower bitrate target. Detail, text, fades, animation, codec and encoder behaviour all affect the output. Use YouTube’s general recommendations as a reference, then assess quality and stream health in a realistic test.
Is 60 fps necessary for an image slideshow?
Usually, still slides alone do not give you a reason to choose 60 fps. Start by considering 30 fps, then test a higher rate if smooth motion or transitions are important to the design. Remember that the higher frame-rate row has a different YouTube recommendation and may require more capacity.
How do I loop an image slideshow in OBS?
Add an Image Slide Show source, choose the images or directory, set the order and timing, and ensure Loop is enabled. OBS documents looping as on by default, but confirm the setting in the source properties and test the transition from the last image back to the first. If your playlist contains video or audio files, use the VLC Video source instead.