A timer-based slideshow can rotate album art in OBS, but it will not automatically know which track is playing. If you need each cover to match its track, you need a separate mechanism that detects track changes and updates the image; displaying a request queue does not provide that connection by itself.
The practical starting point is to decide whether timed changes are good enough or whether the artwork must follow the playlist exactly. Then treat the image display, the track or request system, and YouTube chat as separate pieces to configure and verify.
Choose a request queue and overlay
A request queue and an artwork overlay solve different problems. The queue is where requests may be collected or ordered; the overlay is a visual element placed over your broadcast. An overlay can show a queue or other text, but its presence does not prove that it can receive track requests, read the currently playing track, or select the corresponding cover.
Start by writing down what the viewer should see. For example, a devotional channel might want the current bhajan title and its cover, while a lofi station might want a static station identity with covers changing only when the operator updates them. Those are different requirements. If your goal is simply to cycle through a set of images, OBS has an Image Slide Show source. If the goal is exact track-to-cover matching, identify a separate, verified source of track-change information before relying on a tool or workflow.
The OBS Image Sources documentation describes a slideshow that can use image files or a directory and can operate automatically or manually, including hotkey control. It supports BMP, TGA, PNG, JPEG/JPG and GIF images. The documentation gives 8,000 ms as the default slide interval and 700 ms as the default transition speed; those are starting defaults, not recommendations for every channel. A quick visual change may suit a short music loop, while a slower transition may suit an ambience stream. In either case, the timer is not track metadata.
For manual operation, you can prepare covers in playlist order and advance the image at each track boundary. That depends on someone keeping the playlist and slide sequence aligned. For automatic operation, the images change according to the interval or source behaviour you configure, not according to whether a song has ended. A timer can land in the middle of a track or show a cover for the wrong track.
An automated, hands-off match requires a distinct metadata-aware mechanism: something must identify the current item and cause the correct image to appear. The OBS materials cited here do not establish a particular metadata-aware implementation, so do not treat an unverified plugin, queue service or overlay as a proven solution. If you are still choosing how to run the music itself, the practical trade-offs in running a VLC playlist to YouTube Live may help you separate playback from what the scene displays.
Add its URL as an OBS Browser Source
A Browser Source displays a web page inside an OBS scene. If the queue or overlay provider gives you a display URL, add that URL as a Browser Source and configure its dimensions to fit the area where the page should appear. This only loads the displayed page. It does not establish that the page can control playback, find album art, or accept YouTube chat requests.
In OBS, add a Browser Source to the scene where you want the queue or overlay. Use the supplied display URL and set width and height to match the intended region of the canvas rather than making the source larger than the scene. If the overlay has a transparent background, confirm that transparency is part of the provider's instructions; otherwise a solid page background can cover the video or artwork behind it. Avoid assuming that a URL used for a browser preview is also the correct URL for an OBS source. Check the provider's own setup instructions and use the display address intended for broadcasting.
Keep source roles clear. The Browser Source may show request titles or queue status. The OBS Image Slide Show source, by contrast, displays a set of images. You can use both in one scene, but placing them together does not wire one to the other. If the overlay's queue changes while the slideshow continues on a timer, that is expected unless you have verified a separate connection that updates the image on track changes.
A useful first test is to load the Browser Source in an otherwise simple scene with a temporary background. Check that the page appears, text is readable at the final canvas size, and any intended transparency behaves as expected. Then inspect the scene at the size viewers will see it, not just at a close zoom in the editor. For a stream made with an encoder, keep the video feed and its live-ingestion settings as a separate concern; the YouTube encoder guidance covers the broadcast side, not the queue's ability to update covers.
Position the queue in the scene
Position the overlay so it adds context without competing with the artwork or obscuring essential parts of the video. In OBS, select the Browser Source and use the transform controls to place and size it. A small queue panel along an edge may be enough for a music channel; a full-width panel can make more sense for a request-focused programme, but it may leave less room for the cover itself.
Before settling on a location, preview a scene containing the actual background, album art, queue and any channel branding. Check the likely range of cover colours and title lengths. White text that reads over a dark cover may disappear over a pale one; a queue panel that looks tidy over a plain background may obscure a face, lyric text or important visual detail once the real scene is running. Use the overlay's own background or text options if available, but verify the result at normal viewing size.
Think about cropping and safe margins as well. A source positioned flush to an edge can look cramped, and an overlay can be partly obscured if another source is layered above it. In OBS, source order matters: a higher source in the list can appear in front of a lower one. Check both the source order and the visual boundaries after moving or resizing the overlay. If you change the scene canvas or output format, repeat the check rather than assuming the old placement still fits.
Keep the cover image and the queue visually distinct. If the current track is the main information, give its title and art priority, and avoid making a long request list so prominent that viewers mistake it for the current song. If the queue is only supplementary, show a limited amount of text or use a compact display, where the provider supports it. The result should still make sense to a viewer who has just joined and has not seen the previous track change.
For a channel that must remain live overnight, scene layout is only one part of the setup. The unlisted-stream testing checklist offers a useful reminder to check the complete output before relying on it, rather than judging a component in isolation. Test the scene with representative audio and images, and inspect it after the stream has been running long enough to observe an actual change.
Connect the overlay to its request mechanism
A visible queue is not a request system, and a request system is not automatically an album-art controller. The queue may be a read-only page, a list populated by a separate service, or a visual element that depends on configuration elsewhere. Confirm what the provider actually documents before telling viewers they can submit requests or assuming that a request will change the current cover.
Map the flow in plain language before connecting anything: where a viewer submits a request, where the request is accepted or moderated, what determines the playback order, how the current track is identified, and what tells the image source to update. If any of those steps are not accounted for, you do not yet have an end-to-end request-and-artwork workflow. In particular, a Browser Source URL only addresses display inside OBS. It does not show that YouTube chat is being read, that a requested track is available, or that track metadata is matched to an image.
If you use a human operator, define the manual hand-offs. For example, an operator can approve a request, place it into a playlist, and advance a hotkey-controlled slide when that track begins. This can be straightforward for a small, staffed show, but it depends on attention and an agreed order. A 24/7 channel has to account for periods when nobody is watching the controls. A timer-based slideshow can continue in that period, but it remains timed rotation rather than exact synchronization.
If you are evaluating a queue or overlay provider, look for documentation that states what inputs it accepts and what it changes. Ask whether it only displays queue data, whether it has a separately configured request source, and whether it documents any action when the current track changes. Test those functions independently. Do not infer integration from a marketing screenshot or from the fact that a queue appears inside OBS.
This separation matters when requests fail. If the queue page is visible but no request appears, investigate the request mechanism rather than changing image timing. If the queue advances but the cover does not, inspect the playback-to-art update path. If neither changes, check the source page and its connection. Keeping a short record of what each component is meant to do makes diagnosis less guesswork, especially if you return to the setup after several days.
Test refreshes and track changes
Test the behaviours separately before leaving the channel unattended. First, verify the image source by itself: confirm that every image loads, that the order is what you expect, and that automatic, manual or hotkey operation behaves as configured. OBS's documented defaults of 8,000 ms for interval and 700 ms for transition are not a promise that those timings match your tracks. Choose settings for the actual show, and check the transition does not make text or covers difficult to read.
Next, test the queue page refresh. Observe whether the displayed list updates after a change made through the queue's documented mechanism. Check whether a refresh is required, whether the page updates itself, and whether a browser reload causes an empty, stale or duplicated display. These are properties to verify for the particular overlay and queue you use; do not assume that every Browser Source refreshes in the same way or that a page update also changes the image source.
Then test a track change. Use a short, controlled sequence with known titles and covers, and compare the song that is actually playing with the cover on screen. If you are advancing manually, test the hotkey and make sure it advances exactly once at the intended boundary. If you expect an automatic system to match track metadata, verify that specific behaviour with multiple changes and a restart. A successful page refresh alone is not evidence of track synchronisation.
A compact verification checklist is useful before a long broadcast:
- Every intended cover loads and displays at the planned size.
- The slideshow order, timer or manual control matches the chosen approach.
- The queue display updates after a known queue change, and its refresh behaviour is understood.
- The displayed current track and cover match after a track boundary, if exact matching is required.
- A reload or OBS restart does not leave the scene showing an unintended stale state.
- The audio and moving visuals reach YouTube as expected, and stream health is monitored.
Run this check with the actual kind of audio and scene movement you plan to broadcast. YouTube Help says, “Make sure to test before you start your live stream.” It also recommends monitoring stream health. That advice applies to the composed broadcast and its delivery; it does not certify the queue or album-art connection. For other encoder concerns, such as a stream that drops frames during scheduled backups, keep the diagnosis distinct from overlay refresh problems.
Verify YouTube chat compatibility
A queue shown in OBS does not establish that YouTube chat can submit requests to it. Chat compatibility depends on a separately documented connection between YouTube chat and the request mechanism. Check the provider's own documentation for the exact supported source and setup, rather than relying on a queue being visible on screen or on a generic claim that chat is supported.
Verify the intended workflow with a controlled test before inviting viewers to use it. Confirm where a test message is submitted, how it appears in the queue, whether a moderator or other step is required, and what happens to a rejected or unavailable request. Then check whether accepted requests affect playback, and separately whether the cover changes to the matching art. These are different outcomes; success at one stage does not prove the next stage works.
If you cannot confirm an end-to-end connection, describe the feature narrowly to viewers. You might say that a queue is displayed, or that requests are being handled manually, only if that is what you have tested. Do not imply that messages in YouTube chat automatically become tracks or that they cause the cover to update. Keep a fallback ready, such as turning off request instructions or returning to a known playlist, if the queue or connection stops behaving as expected.
YouTube's live encoder guidance is about sending a valid broadcast, not connecting chat to a third-party queue. Likewise, YouTube's Live Streaming API documentation describes broadcast and stream resources, including recurring and continuous broadcast concepts; it does not configure an OBS image source or verify a particular request overlay. Keep platform-level documentation and tool-specific evidence separate.
Keep the always-on stream maintainable
An artwork workflow that works for one song should also be manageable when the channel repeats for hours. Keep image files named or grouped in a way that makes playlist order clear, and preserve a copy of the intended set. If a cover is replaced, check that the image source points to the new file and that the new artwork does not change the scene's readability. A manual workflow benefits from a simple operating note: the playlist order, the key that advances the slide, and what the operator should do if the order slips.
Plan for the less interesting failure cases. A page may load slowly, a queue may stop refreshing, a track may not have a usable cover, or an operator may restart OBS and return to a different source state. Decide what viewers should see in those cases. A neutral channel image or a static station card can be a more honest fallback than leaving an incorrect cover on screen. The appropriate fallback depends on whether the artwork is decorative or is being presented as information about the current track.
For a continuous YouTube broadcast, artwork is only part of the output. Audio continuity, encoder health and YouTube ingestion requirements remain separate responsibilities. YouTube also documents HLS ingestion, which requires an HLS-capable encoder and specific playlist, segment and transport settings; its documentation notes higher latency than RTMP. HLS is an ingestion choice, not a way to synchronise album art. You can review the HLS setup requirements if that delivery mode is relevant to your encoder.
If you are using OBS on a computer, consider what happens when that computer or its connection needs attention overnight. A cloud-based route can remove the need to keep your own computer switched on for the broadcast, but it does not remove the need to prepare and verify the file and channel. StreamNeo is useful where the specific burden is leaving a computer running to keep a prepared video live; it does not turn a displayed queue into track-aware art or establish YouTube chat request integration. Keep those requirements in your test plan whichever way you run the 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
Does OBS rotate album art automatically when a song changes?
OBS's Image Slide Show can rotate images automatically on a timer, or you can operate it manually or by hotkey. Its documented slideshow behaviour does not identify the current song and select that song's cover. Exact matching needs a separate, verified track-aware mechanism.
Can I use a Browser Source overlay for requests?
A Browser Source can display a web page in an OBS scene, including a queue page when the provider supplies a suitable display URL. That alone does not show that YouTube chat feeds requests to the queue, or that a request changes playback or artwork. Verify each connection in the provider's documentation and with a controlled test.
Is a timed slideshow suitable for a 24/7 music channel?
It can be suitable when changing images on a timer is acceptable or when an operator can keep manual changes aligned with the playlist. It is not a reliable substitute for track-synchronised covers when exact identification matters. Decide what viewers are being told by the artwork before choosing the simpler approach.
What should I test before leaving the stream running?
Check that images load, the queue refreshes as expected, and the cover follows a track change if that is a requirement. Test the full audio and visual output on YouTube, and monitor stream health. Do not treat a visible queue or a successful page reload as proof that chat requests, playback and artwork are connected.