Starting Soon Screen [2026]: 3 Formats, $0 to $27/mo
![Starting Soon Screen [2026]: 3 Formats, $0 to $27/mo](https://ivipid.com/blog/wp-content/uploads/2026/11/starting-soon-screen-loop-vs-browser-vs-image-2026-gen-1024x585.webp)
Starting Soon Screen Verdict: Loop, Browser Source or Image · What OBS Studio 33 Changed for Starting Soon Scenes · Video Loop: The Self-Contained Starting Soon Screen · Browser Source: The Live Countdown Route · Static Image: The Starting Soon Screen That Cannot Fail · Render Settings for Each Format · Starting Soon Screen Makers Compared: Price and Free Plan · Load and Reliability: What the Sources Show and What to Measure · Twitch vs YouTube Live: Does the Platform Change the Choice? · Six Setups and the Format Each One Picks · Migration Guide: Moving Between Formats · Pros and Cons of Each Format · Verdict: Build the Layered Starting Soon Screen · Questions creators ask
A starting soon screen reaches your viewers in one of three ways inside OBS: a looping video file, a browser source, or a still image. All three work on Twitch and YouTube Live, and all three cost $0 to run in OBS Studio itself. The real choice is what you want the scene to do while people wait: move, count down, or simply stay put without breaking.
The timing matters this month. OBS Studio 33.0 shipped on October 23, 2026, and 33.0.1 followed on October 29. According to Linuxiac’s release coverage, version 33 raised the embedded Chromium Embedded Framework behind Browser Source from version 127 to 150, which touches exactly one of the three formats. OBS posts its own change lists on obsproject.com, and the 32.2 notes are the newest official blog post I could confirm there, so treat the third-party coverage of version 33 as reported rather than final.
This comparison puts the three formats side by side on specs, failure modes, price and setup time, then looks at what Streamlabs, StreamElements, OWN3D, Canva and Placeit give you for free. If you want click-by-click build steps instead, our 11-step starting soon screen guide for OBS covers the build. This page helps you decide what to build first.
Starting Soon Screen Verdict: Loop, Browser Source or Image
Short answer: use a video loop as the visual base, add a browser-source countdown on top only if your start time is fixed, and keep a static image scene ready as a fallback. That layered setup costs $0 in OBS and survives most things that go wrong five minutes before you go live.
If you must pick exactly one, the static image wins on reliability, the video loop wins on polish and audio control, and the browser source wins on live data. The table below lays out thirteen specs that decide which one fits your channel. Every row is a property of how OBS handles the source, not a vendor claim.
| Spec | Video loop | Browser source | Static image |
|---|---|---|---|
| OBS source type | Media Source | Browser Source | Image Source |
| What you hand OBS | MP4 or WebM file on disk | A URL or a local HTML file | PNG or JPG file on disk |
| Motion | Any pre-rendered animation | Anything a web page can animate | None |
| Live countdown to a set time | No, unless you layer another source | Yes, the page runs its own timer | No, unless you layer another source |
| Audio from the file itself | Yes, mixed in OBS | Yes, if you route page audio through OBS | No |
| Needs the internet | No | Only for hosted pages, not local files | No |
| Typical failure | Visible jump at the loop point | Blank scene if the page is down | Looks frozen to viewers |
| Processing cost | Video decode while the scene is live | A browser instance, cost depends on the page | Lowest of the three |
| Edit after you publish | Re-render the video | Change the page, no re-render | Swap the file |
| Resolution you author at | 1920×1080 for a standard canvas | 1920×1080 browser size for a full scene | 1920×1080 canvas-sized file |
| Update after OBS 33 | No change expected | Test it, the browser engine moved | No change expected |
| Cost to make (own tools) | $0 with a free editor | $0 with a hosted template or your own HTML | $0 with a free design tool |
| Best for | Branded waiting room with music | Scheduled starts and event streams | Low-effort, zero-risk channels |
Read the table top to bottom and the pattern is clear. Each format fixes exactly one weakness of the others. A loop adds motion but cannot count. A browser source counts but can fail blank. An image never fails but never moves. The sections below take each in turn.
What OBS Studio 33 Changed for Starting Soon Scenes
OBS Studio is free and open source, runs on Windows 10 and 11, and needs macOS 13.0 or newer on Mac. Version 33.0 arrived on October 23, 2026 after a run of release candidates, and 33.0.1 followed on October 29 as a maintenance release. The official OBS site still lists the 33 line as the current one, with no newer stable release showing as of November 15.
Two changes reported around the 33 release matter here. First, the Chromium jump from 127 to 150 affects Browser Source and browser docks directly. Pages built on mainstream web features should keep working. Pages that lean on old CSS tricks, odd font loading or long-dead JavaScript are the ones worth opening in OBS before you update a channel that streams tonight. Second, reports describe a redesigned plugin-loading behavior. If your starting soon scene depends on a plugin (a countdown plugin, a stinger helper or a multistream tool), check that plugin’s page for 33 support before you update.
Nothing I found describes a change to Media Source or Image Source in 33. That fits the practical advice: a loop or an image should behave the way it did in 32.x. A newer Chromium build is as likely to improve a hosted page as to break it, but a test costs two minutes and a failed start costs an audience. For the wider set of overlay scenes around this one, the Stream Intros and Overlays hub collects our other comparisons.
One more version note. The most common installed version in a third-party tracker was still 32.2.2 around the 33.0.1 release, and a separate project called OBS-Studio-Rust reportedly reached 1.0.0 on November 1, 2026. That project is not OBS Studio. If a template, plugin or forum answer mentions it, check which program the author means before you follow the steps.
Video Loop: The Self-Contained Starting Soon Screen
A video loop is a pre-rendered clip that OBS plays through a Media Source. You build it in any editor, export an MP4 or WebM, point the source at the file, and tick Loop. It is self-contained animation that does not depend on an external web page, though it generally lacks live widgets unless you layer other sources over it.
The big upside is control. You decide every frame, including the music bed under it. The loop can carry a logo reveal, animated text, a looping background and a soft audio track, and OBS mixes the file’s audio like any other source. That is the main reason loops feel more finished than an image. The cost is the loop point. If the last frame does not match the first, viewers see a jump every time the clip restarts, and a five-minute wait shows that jump many times.
Make the loop point disappear
Design the clip so motion starts and ends in the same pose. A slow drifting background, a logo that breathes in and out, or particles that wrap around the frame all loop cleanly. Avoid one-way moves such as a title that flies in once and stops, because the restart exposes it. If the file carries music, fade nothing at the end. Loop the music bed at the same length as the picture, or keep the music as a separate audio source so the picture can loop on its own timing.
Inside OBS, the properties that matter are Loop (on), Restart playback when source becomes active (on, so every visit to the scene starts from frame one), and Close file when inactive (a memory saver that releases the file when the scene is off-screen). If your computer struggles, hardware decoding in the same dialog is worth trying. Keep the file at your canvas size. A 4K clip on a 1080p canvas makes OBS decode pixels it throws away.
From the Vipid archive: the animated logo intro theme is one example of a short logo animation you could drop into the centre of a loop, and its page lists resolution, length and frame rate so you can check it against your canvas.
Where a loop falls short
A loop cannot tell time. If you bake the words Starting in 5 minutes into the file, you either rebuild the clip for every stream or leave the text vague. Most loop users solve this by layering a text source or a browser-source timer on top, which is a perfectly good setup but means the loop is a background, not the whole screen. A loop also needs a render step whenever your brand changes. For a channel that updates its look every season, that is a small cost. For a channel that updates the schedule line every week, it is an annoyance.
Browser Source: The Live Countdown Route
A browser source loads a web page inside OBS. That page can be a hosted overlay from a maker, a page you wrote yourself, or a local HTML file on your drive. Because the page runs real JavaScript, it can count down to an exact time, rotate sponsor lines, show your schedule or play a looping animation, all without a re-render.
That flexibility is why event streams and scheduled shows lean on it. A countdown that reads 02:14 and ticks to 00:00 tells viewers exactly when the show begins, and it keeps them in the stream instead of refreshing the page. Many makers deliver their starting soon scenes as a browser-source link for this reason. OWN3D’s official alert guide, for example, recommends a 1920 x 1080 resolution when you use a Scene Builder link and 800 x 600 for a single alert browser-source link. The same pattern applies to scenes: set the source size to match what the page was designed for, then scale in OBS if needed. Alerts follow the same browser-source logic, and our Twitch alerts comparison of three makers covers how those links behave.
Local file or hosted URL
A hosted URL depends on someone else’s server being up and your login still being valid. If the maker’s page is slow, you get a slow scene, and if it is down, you get a blank one. A local HTML file avoids that. Tick Local file in the browser-source properties, point it at an index.html on your drive, and the page loads from disk. You lose maker-hosted updates, but you gain a scene that works offline. For a fixed-time countdown, a local page is the sturdier choice.
Two more properties earn their keep. Shutdown source when not visible stops the page from running while another scene is live, and Refresh browser when scene becomes active reloads the page on every visit, which resets a countdown that you adjusted. If you want the page’s audio in your mix, use Control audio via OBS so the sound shows up as its own channel in the audio mixer.
A minimal local countdown page
This is a small page you can save as index.html and load as a local file. Change the target date and time to your own start, and it counts down to zero then shows a Going live message. It carries no external scripts, so it keeps working with no connection.
<!doctype html>
<html>
<head>
<meta charset="utf-8">
<style>
html, body { margin: 0; background: transparent; }
#t { font: 700 160px system-ui, sans-serif; color: #fff;
text-align: center; padding-top: 380px;
text-shadow: 0 4px 24px rgba(0,0,0,.6); }
</style>
</head>
<body>
<div id="t"></div>
<script>
const target = new Date("2026-11-20T19:00:00").getTime()
const el = document.getElementById("t")
function tick() {
const s = Math.max(0, Math.round((target - Date.now()) / 1000))
const m = String(Math.floor(s / 60)).padStart(2, "0")
const r = String(s % 60).padStart(2, "0")
el.textContent = s === 0 ? "Going live" : m + ":" + r
}
tick()
setInterval(tick, 500)
</script>
</body>
</html>
Set the browser source to 1920 x 1080, layer it over a loop or an image, and the transparent background lets the art show through. The date above is a placeholder, so replace it before use. For minutes beyond 99, the minutes field simply grows to three digits, which is fine for a long pre-show.
Static Image: The Starting Soon Screen That Cannot Fail
An Image Source shows a PNG or JPG. That is the whole feature. There is no decoder to stall, no page to time out and no loop point to expose. When the stream is going wrong and you need a scene that works right now, this is the scene you switch to.
The weakness is perception. A still frame with no movement can look like a frozen feed, and viewers who see nothing change for a minute sometimes leave to check whether the stream broke. You can soften that without a video: add a music bed through a separate audio source, put a small animated element such as a webcam frame or an alert test on top, or layer a text countdown. Even a slow ticking clock rescues a still image from looking dead.
Static images also make the best fallback in a layered setup. Keep a Starting Soon (still) scene next to your Starting Soon (loop) scene. If the media decode hiccups or the browser page fails, one click moves you to the image and you lose nothing in front of the audience. OBS also offers an Image Slide Show source, which cycles through several stills on a timer. It sits between a still and a loop and suits channels that want rotating sponsor cards without any video editing.
Make the image at the canvas size, usually 1920 x 1080, and save text-heavy art as PNG so edges stay sharp. JPG compresses photographic backgrounds well but smears fine text. If you are using OBS’s Unload image when not showing option, expect a tiny delay when the scene first appears. For most channels that delay is invisible.
Render Settings for Each Format
These are the settings I would start from. The 1920 x 1080 sizes match what OWN3D’s own setup guide recommends for Scene Builder links and what a standard 1080p canvas expects. Frame rate, length and codec are editorial defaults you can change, not vendor requirements.
| Setting | Video loop | Browser source | Static image |
|---|---|---|---|
| Resolution | 1920×1080 | 1920×1080 source size | 1920×1080 |
| Frame rate | Match your OBS canvas frame rate | Match your OBS canvas frame rate | Not applicable |
| Length | Short enough to author a clean loop, long enough that the repeat is not obvious | Runs until you change scenes | Not applicable |
| Export format | MP4 with H.264 video and AAC audio, or WebM | HTML page, local or hosted | PNG for text, JPG for photos |
| Audio | In the file, or leave silent and use a separate music source | Route through OBS, or leave silent | Use a separate music source |
| Transparency | Needs a format that carries alpha, so test before you rely on it | Transparent page background | PNG supports transparency |
| Source property to set | Loop on, restart on activate | Local file, shutdown when hidden | Nothing special |
If you do not want to design the motion yourself, the Vipid intro themes list shows resolution, length and frame rate for each original theme, which is the same checklist you need for any loop source. Whatever you choose, match the loop’s frame rate to your canvas. A 24 fps clip in a 60 fps scene works, but motion can look slightly uneven, and a mismatch is the first thing to check if a loop looks off.
If you already have a still image and want it as a loop source (for example to add an audio track), this one FFmpeg command turns it into a ten-second MP4. The length, rate and codec flags are my starting values, so adjust them to your canvas.
ffmpeg -loop 1 -i start.png -i music.mp3 -t 10 \
-c:v libx264 -pix_fmt yuv420p -r 30 \
-c:a aac -shortest start-loop.mp4
Starting Soon Screen Makers Compared: Price and Free Plan
You can build all three formats yourself at $0, and many creators do. Makers earn their place by saving design time, so the question is what each one hands you for free and where the paywall sits. The table collects what I could confirm. Where a price is not listed, the cell says so instead of guessing.
| Tool | What you get free | Paid layer | How it reaches OBS |
|---|---|---|---|
| OBS Studio 33.0.1 | Everything: scenes, sources, recording, streaming, no watermark | None, it is free and open source | It is the host program |
| Streamlabs | A free tier with basic overlays and themes | Ultra at $27/month or $189/year (about $15.75/month on the annual plan) | Streamlabs Desktop, or an official Plugin for OBS |
| StreamElements | Free customizable alerts and widgets, per its own site | Not confirmed on the pages I read | Browser source link or its own OBS tool |
| OWN3D Pro | Free alerts after registration | Stream Pass for premium designs, price not published on the pages I read | Scene Builder link or single browser-source link |
| Canva | Design tool for stills and short animations | Plan prices not confirmed from an official page | Export a file, then Image or Media Source |
| Placeit | Template library for stream graphics | Plan prices not confirmed from an official page | Export a file, then Image or Media Source |
What you get on the free plan, tool by tool
OBS Studio: the full program at $0 with no account and no watermark. It has no built-in template library, so you bring your own art. That is the baseline every maker below competes against.
Streamlabs: the Streamlabs Cross Clip pricing page lists Ultra at $27 a month, and third-party pricing reports dated early November 2026 add the $189 yearly price. One of those reports describes the free Starter plan as including basic overlays and themes, two destinations, one guest, no-fee tipping, 1 GB of storage and a basic Cloudbot, so treat that feature list as reported. The same reports say Ultra opens a library of more than 1,000 overlays and themes. A design-cost roundup from Mark Studios, read November 14, 2026, puts Ultra themes at $15.75 a month, which matches the $189 yearly price divided by twelve. Streamlabs also lists an official Plugin for OBS if you prefer to stay in OBS Studio.
StreamElements: its own site advertises free customizable alerts and widgets for live streamers. A banner on the site also says StreamElements is now part of Razer, with updated Terms of Use effective August 1, 2026. A banner is not a pricing change, so there is no sign that the free tools moved behind a paywall. Its overlay editor outputs browser-source links, which makes it a natural source for a countdown layer.
OWN3D Pro: OWN3D’s guide updated on October 30, 2026 says free alerts are available after registration and premium designs sit behind the Stream Pass. The pages I could read do not publish the Stream Pass price, so I will not give one. Its Scene Builder produces a link you add as a browser source, and the guide recommends 1920 x 1080 for that link. For a deeper look at free overlay sources and where each one gates its extras, see our free Twitch overlays comparison.
Canva and Placeit: both are design-and-template services that export files, so they feed the video-loop and still-image routes rather than the browser-source route. I could not confirm current plan names, export limits or prices for either from an official page today. A third-party listing reported Placeit paid plans starting at $1.99 a month, but that is a single-source claim, so check Placeit’s own pricing page before you rely on it. Before you pay either one, confirm the three limits that decide a starting soon screen: export resolution, clip length and whether the watermark comes off.
What custom designers charge
If you would rather pay a person, a Mark Studios roundup read on November 14, 2026 collects other designers’ published prices. It reports $60 to $1,500 for a full custom stream package and $25 to $225 per individual piece. Those figures belong to the designers it surveys, not to Mark Studios, and they are the best public price range I found for custom work.
| Item | Price reported | Designer cited |
|---|---|---|
| Static offline screen | $150 | Fuzey Designs |
| Animated offline screen | $188 | Fuzey Designs |
| Webcam frame, static | $25 | StreamerOverlays.com |
| Webcam frame, animated | $55 | StreamerOverlays.com |
| Stinger transition | $50 to $150 and up | StreamerOverlays.com |
| Stinger transition | $150 | Fuzey Designs |
| Alert kit, four alerts plus a frame or bar | From $100 | StreamerOverlays.com |
The pattern in those numbers is useful on its own. Fuzey’s animated offline screen costs $38 more than its static one ($188 against $150), so a designer prices motion as a modest premium, not a different product. Offline screens are the closest listed item to a starting soon scene, so read them as a guide rather than a quote. The same roundup says to put turnaround and revisions in writing, and it cites Streaming Vault quoting 7 to 10 days for its first tier and 30 days for its $950 tier. If a stream date is fixed, turnaround matters as much as price.
Load and Reliability: What the Sources Show and What to Measure
No source I found publishes CPU or GPU benchmarks that compare a looping Media Source, a Browser Source and an Image Source on the same machine. I will not invent a percentage. What the vendor and release material do give is direction: a still image is the lightest option, a decoded video adds work while its scene is active, and a browser page costs whatever the page demands. Official OBS pages describe sources and release changes but publish no per-source cost figures, and the third-party coverage of version 33 describes the Chromium change without any measured cost either.
That leaves you to measure it on your own rig, which takes ten minutes. Build the three scenes, switch to each one, and watch the Stats dock (View, Docks, Stats). Three numbers tell the story: CPU usage, missed frames due to encoding lag and skipped frames due to rendering lag. If a scene pushes any of them off zero, that format is too heavy for the moment, and you pick a lighter one or shrink the source.
- Test while streaming, not idle. Start a private or test stream so the encoder is running, because decode cost on a quiet system hides problems.
- Test the longest wait. Leave each scene up for the full length of your usual pre-show. Memory growth and loop-point glitches show up late.
- Test after every OBS update. The version 33 browser-engine change is the reminder. A two-minute check after each update beats a failed start.
- Test the fallback. Switch from the loop to the still image while live and confirm the audio and scene transition behave.
Reliability, unlike load, has clear answers from how each format works. A still image has no moving parts. A loop has one (the decoder and the file). A hosted browser page has several (the network, the maker’s server, your login and the page’s own code). A local browser page drops the network pieces. Rank them by the number of things that can break and you get image, then loop, then local page, then hosted page. That ranking matches what the vendor guidance repeats: images are the safest choice, and browser sources suit live elements.
Third-party commentary lines up too. Several of the sources I checked say the same thing in different words: use a still when reliability matters most, a loop when you want controlled motion and audio, and a browser source when the design must change live. None of them offers measured data, so I treat the agreement as informed opinion, not as a benchmark.
Twitch vs YouTube Live: Does the Platform Change the Choice?
Not at the source level. OBS sends your scene to either platform as ordinary video, so a loop, a browser page and an image behave identically on Twitch and YouTube Live. I found no official Twitch or YouTube document that sets a format requirement for a waiting scene, and the recent announcements from both platforms point elsewhere.
YouTube’s Made on YouTube 2026 announcements introduced Live Showdowns, an expanded Watch With feature, creator matchmaking and a pilot of real-time Live auto-dubbing. In its official 2026 announcement post YouTube positions these as audience and collaboration features, not changes to how an OBS scene is built. YouTube also said that in August 2026 more than 600 million logged-in viewers watched live content each day, archive viewing included, so a waiting scene may be seen by a large audience, though most channels see only their own slice of it. YouTube’s creator-updates page reportedly lists Live Practice Mode, a private rehearsal before going live, rolling out in the mobile app, which helps phone streamers more than OBS users.
On Twitch, TwitchCon San Diego 2026 brought Stream Recaps, clip-editing tools and a five-minute maximum Clip length, announced November 13. None of that changes a starting soon scene. One Twitch detail does touch countdowns. Twitch’s Partner page says Partners can delay their broadcast by up to 15 minutes in competitive play. If you run a delay, viewers see your countdown reach zero later than you do, so a hard 00:00 can mislead them. For delayed streams, show the target time as a clock time and add a line such as Stream starts shortly after zero.
YouTube adds one practical difference. A scheduled live event has a public waiting-room page that viewers see before you start, so your scene matters only once the stream is live. If you stream to both platforms, build one scene at 1920 x 1080 and reuse it. Anything platform-specific, such as a handle or chat prompt, belongs in a separate layer you can switch off. StreamYard also publishes a guide on using OBS for live streaming and when StreamYard is easier, which is worth a read if you want a browser-based studio instead of local scenes.
Six Setups and the Format Each One Picks
These are composite setups built from common creator situations, not named channels or measured results. Each one lists the pick, the reason and the one thing to watch.
1. The solo variety streamer with a brand. Goes live around the same time most nights and wants a polished waiting room. Pick: video loop with a music bed, plus a small text countdown. Reason: the loop carries the brand and the audio, and the timer is a layer, so nothing needs rebuilding each stream. Watch: the loop point. Test it by watching two full cycles.
2. The tournament organiser. Runs scheduled matches with a published start time and sponsors to show. Pick: local-file browser source. Reason: the countdown is exact, sponsor lines rotate without a render, and a local file stays up if the venue network drops. Watch: after each OBS update, open the page and confirm fonts and animation still look right, because the Chromium engine changed in version 33.
3. The webinar or talk host on YouTube Live. Needs a clean holding slide with the title, the speaker and a start time. Pick: static image. Reason: nothing animated is required, and the slide never fails. Watch: viewers may read a frozen slide as a dead feed, so add quiet music and say in the title text when the talk starts.
4. The new streamer on a modest laptop. Encoder load is already high and every spare percent counts. Pick: static image first, then try a loop and read the Stats dock. Reason: a still is the lightest source in the vendor guidance, and you keep the upgrade path open. Watch: skipped frames in Stats when you switch to the loop. If they rise, stay with the image.
5. The channel with a logo reveal it likes. Already has a short logo animation from an intro project. Pick: render the reveal into a loop with an idle background after it, then use it as the Media Source. Reason: you reuse existing art. Watch: make the end state match the start state, or the restart will look like a cut. An intro maker’s output can feed a waiting scene this way, provided you export at your canvas size.
6. The podcaster streaming video. Goes live with a cover image and a host name. Pick: static image with a music bed as a separate audio source. Reason: a podcast audience cares about sound over motion, and a still never competes with the audio. Watch: duck the music when the host starts talking, then mute the source so the scene switch is clean.
Quick recommendations by use case
- Fixed start time, any platform: local browser source countdown over a loop or still.
- Branded nightly stream: video loop with music, a text timer on top.
- Lowest risk and lowest load: static image, music as a separate source.
- Sponsor rotation without re-rendering: browser source or Image Slide Show.
- Reusing an existing logo animation: render it into a loop at canvas size.
- Dual-platform streams: one 1920 x 1080 scene, platform-specific text on a separate layer.
Migration Guide: Moving Between Formats
Most channels start with an image and graduate. The steps below move you from one format to the next without touching your live scenes until the new one is proven.
Image to loop
- Duplicate your starting scene and rename the copy so the original stays intact.
- Render the loop at your canvas size. If you start from your still, the FFmpeg command above makes a first version in one line.
- Add a Media Source to the copy, tick Loop and Restart playback when source becomes active.
- Watch two full cycles for a visible jump at the loop point and fix the clip if you see one.
- Open the Stats dock during a test stream and confirm no new skipped or missed frames.
- Swap the copy in once it passes, and keep the still scene as the fallback.
Loop to browser source
- Pick a local page (like the countdown above) or a maker’s hosted link.
- Add a Browser Source above your loop and set it to 1920 x 1080.
- For a local page, tick Local file and select the HTML. For a hosted page, paste the URL.
- Tick Shutdown source when not visible and Refresh browser when scene becomes active.
- Check that the page background is transparent so the loop shows through.
- Set the real target time and confirm the countdown against a clock.
Changing makers
Hosted scenes from Streamlabs, StreamElements or OWN3D are links, not files, so leaving one means rebuilding the scene. Before you cancel a paid plan, export or screenshot every scene, note the exact source sizes and keep a still-image copy. After cancelling, test every hosted scene. Some pages stop loading or show a watermark. A scene you built from your own files has no such risk, which is the quiet argument for exporting a local copy of anything you plan to use for a year.
Pros and Cons of Each Format
Video loop
- Pro: complete control of motion and audio in one file.
- Pro: works offline with no browser components.
- Pro: reusable across platforms and OBS versions.
- Con: cannot show a live time without a second source.
- Con: a bad loop point shows on every repeat.
- Con: any text change means a re-render.
Browser source
- Pro: live countdowns, schedules and rotating text with no render.
- Pro: hosted links update without touching your files.
- Pro: works with transparent backgrounds over any other source.
- Con: a hosted page can fail blank if the server or login breaks.
- Con: cost depends on the page, and you must test it.
- Con: the OBS 33 browser engine change means a post-update check.
Static image
- Pro: the simplest and least failure-prone option.
- Pro: the lightest load of the three.
- Pro: trivial to update, since you swap one file.
- Con: no motion, so it can look frozen.
- Con: no live data without extra sources.
- Con: no audio of its own.
Verdict: Build the Layered Starting Soon Screen
The data points to a layered setup, not a single winner. OBS Studio 33.0.1 costs $0, a local countdown page costs $0, and a loop made in a free editor costs $0, so the full stack needs no budget. Paid layers start where design time gets expensive: Streamlabs Ultra at $27 a month ($189 a year, about $15.75 a month), or a custom offline screen at $150 static and $188 animated in the designer prices Mark Studios collected on November 14, 2026.
Here is the order I would build in. First, a static image scene, because it takes minutes and gives you a fallback. Second, a video loop scene with music, because it is the best-looking waiting room and carries your branding. Third, a local browser-source countdown on top, but only if your start time is fixed. Test all three in the Stats dock after each OBS update, and treat the version 33 Chromium change as your cue to check the browser layer first.
If you stream on a modest machine or you never set a fixed time, stop at the image or the loop. You lose nothing important. If you run scheduled events, the countdown earns its keep, and a local file is safer than a hosted link. Pay for a maker only when its library saves you more hours than the plan costs, and confirm the export limits first, since Canva’s and Placeit’s current limits were not confirmable from an official page for this comparison.
Questions creators ask
What size should a starting soon screen be?
Match your OBS canvas. For most streams that is 1920 x 1080. OWN3D’s own guide recommends 1920 x 1080 for Scene Builder links, so make the image, the loop and the browser source all that size.
Is a video loop or an image better for a starting soon screen?
The loop looks better and carries audio, while the image is more reliable and lighter. Many channels use both, with the loop as the main scene and the image as the fallback.
Did OBS Studio 33 break browser sources?
I found no report of a break. Linuxiac reported that version 33.0 moved the embedded browser engine from Chromium Embedded Framework 127 to 150. Open each browser-source scene after updating and confirm fonts, animation and transparency still look right.
What is the latest OBS Studio version?
OBS Studio 33.0.1, released October 29, 2026, after 33.0 on October 23. The project site shows no newer stable release as of November 15, 2026. OBS is free and open source.
Can I use one starting soon screen on Twitch and YouTube Live?
Yes. OBS sends the scene as ordinary video, so the same scene works on both. Keep platform-specific text on a separate layer you can hide.
Does a stream delay affect my countdown?
It can. Twitch’s Partner page says Partners can delay a broadcast by up to 15 minutes in competitive play, so viewers see the countdown reach zero later than you do. Show a clock time next to the timer on delayed streams.
Which maker has the best free starting soon screen?
It depends on the route. StreamElements advertises free customizable alerts and widgets, OWN3D Pro offers free alerts after registration, and Streamlabs lists a free tier alongside Ultra at $27 a month. For a starting soon scene specifically, I could not confirm a free template from any of them, so compare each one’s template library before you choose.
More from the Vipid blog
- Be Right Back Screen [2026]: 12 Steps in 30 Min
- OBS vs Streamlabs [2026]: $0 vs $27/mo for Ultra
- Twitch Chat Overlay Obs [2026]
- OBS vs ShadowPlay vs Medal [2026]: 3 Free Recorders
- Your Video a channel-style intro theme
- Intro themes stream and channel intros
- Sample videos finished Vipid intros
- Vipid intro maker make a custom intro in the browser
Theo Vance
Theo Vance is the Intros & Templates Editor at Vipid, where he covers intro and outro makers, template libraries for CapCut, Canva and the major editors, slideshow and video-card tools, and stream starting screens. He compares makers on what matters before you hit render: watermark, export resolution, length limits, licence and price, and dates every check. He also looks after the Vipid theme archive, the 2011–2016 intros the site was built on.
![TwitchCon [2026]: Serafim AI Highlights, Booth 1514](https://ivipid.com/blog/wp-content/uploads/2026/11/twitchcon-2026-serafim-ai-highlights-xsolla-gen-800x450.webp)
![Twitch Overlay Size [2026]: 3 Canvases, 3 Formats](https://ivipid.com/blog/wp-content/uploads/2026/11/twitch-overlay-size-2026-gen-800x450.webp)
![Screen Recorder for Mac [2026]: $0 vs $108/yr](https://ivipid.com/blog/wp-content/uploads/2026/11/screen-recorder-for-mac-2026-gen-800x450.webp)