A branded property ticker is a graphic layer in your video scene, not something YouTube automatically adds to a live broadcast. Build it as a hosted web page or local HTML file, place it over the video in an encoder such as OBS, then test how the listings look and move before going live.
The practical work is as much about content and permissions as it is about the overlay. Keep the details readable, confirm you may show the listing data publicly, and check the finished broadcast in YouTube’s preview rather than trusting the scene on your own screen.
Plan the listings and brand treatment
Start with the information a viewer can absorb while the ticker passes once. For each property, that might be a short area or locality, a property type, a price if approved for display, and a route to learn more. Avoid trying to fit every feature, disclaimer, and contact detail into a narrow strip. A ticker is a signpost, not a replacement for a complete listing page.
Decide what remains fixed and what moves. A small brokerage name or logo can sit at one end of the strip while listing cards scroll through a separate area. If everything moves together, the brand may disappear for long stretches; if the logo is fixed, make sure it does not crowd the first or last listing. Use the same colours and type treatment as your other public materials, but give the text enough contrast against the video behind it.
Choose a content order and use it consistently. For example: locality, property type, price, then a short action such as “details on our site”. Keep each item to one or two concise lines if the design permits. Do not rely on colour alone to distinguish a price, status, or category, since the video background and a viewer’s display can affect how colours appear.
Before building the ticker, identify the source for every field. Listing feeds, photographs, prices, and agent details may have conditions on public redistribution, and permission for a website display does not necessarily answer whether a continuous public video broadcast is permitted. Ask the relevant rights holder, listing provider, brokerage, or responsible professional for the rules that apply to your market and agreement. OBS and YouTube documentation describes how to transmit an image; it does not grant rights to the material in it.
If you are also assembling the channel around an existing video, decide whether the listing strip belongs on every scene or only selected portions. A property loop may include exterior footage, maps, and a branded holding screen. The guide to turning existing uploads into a 24/7 live channel can help you think through the underlying loop separately from the ticker layer.
Build a web-page or local HTML ticker asset
The asset can be a web page hosted at a URL or an HTML file stored on the machine running OBS. OBS Browser Source can load either a web page or local file, and its documented controls include viewport dimensions, frame rate, custom CSS, and refresh behaviour. See the OBS Browser Source documentation for the available controls and current platform details.
A hosted page is useful when the ticker needs to be edited from another device or when more than one production machine should load the same source. It also adds dependencies: the page must remain available, its design must work inside a browser viewport, and any remotely updated content needs a dependable source. A local file avoids dependence on a hosted page during broadcast, but someone must update the file on the production machine and verify that the correct version is loaded.
| Route | Useful when | Main trade-off to plan for |
|---|---|---|
| Hosted ticker page | You want to edit content centrally or use a page already maintained online | The page and its data source must be reachable and functioning during the stream |
| Local HTML file | The listings can be prepared in advance and kept with the production assets | Updates require replacing or editing the local file and checking that OBS loads the current version |
| Manually entered listings | You want a short, controlled set of approved items | Someone must review and update each item when details change |
| Externally updated listings | There is an authorised feed and a clear process for changes | Feed terms, field mapping, availability, and update behaviour need their own checks |
For a simple local file, keep the layout straightforward: a transparent or solid ticker background, a fixed brand mark, and repeated listing blocks that move at a steady pace. A page that works in a full browser window may behave differently when reduced to a narrow overlay, so build it for the intended width and height rather than shrinking a complete website. Remove navigation, pop-ups, cookie banners, and elements that have no place in the broadcast.
If you use a remote page, test it with the same browser source and production computer you intend to use. Sign-in prompts, blocked scripts, expired sessions, or unexpected page redesigns can leave an empty or broken strip. For local files, include any images and fonts in a stable location and avoid references to temporary folders. In either case, keep a copy of the last approved version so you can restore it if an update causes problems.
Do not assume that an external property feed is suitable merely because it can be displayed in a browser. Find out whether it allows this specific public use, whether attribution or other notices are required, and how corrections or withdrawn listings should be handled. If those questions are unresolved, use only material you are authorised to publish rather than treating technical access as permission.
Choose a scene for the video and ticker
The ticker is composed into an encoder scene before that scene is sent to YouTube. In OBS, a common arrangement is a background or video source at the bottom, the ticker above it, and any additional title or logo layers in their intended positions. The stack order matters: an opaque background above the ticker can hide it, while an overlay placed over captions or a property feature can obstruct information the viewer needs.
Think of the scene as one complete broadcast frame rather than a video plus an unrelated accessory. Reserve a strip along the bottom or top for the ticker, then check whether the footage still has room to show the property. A small house tour may lose important details if the ticker consumes too much of the frame. Conversely, a narrow strip over an uncluttered street view may work without taking attention away from the subject.
Create a scene at the canvas size you intend to stream, then set the ticker source’s viewport to the dimensions you need for that strip. OBS’s Browser Source settings let you control its viewport independently of the whole scene. This makes it possible to render a page designed specifically for an overlay rather than squeezing a desktop webpage into the frame.
If you are deciding whether to operate a production computer continuously, distinguish the graphics workflow from the runtime choice. A local OBS scene needs the machine running the encoder; other approaches may change where the ongoing work happens. The comparison in used laptop versus Raspberry Pi power considerations is relevant to that separate operating decision, but does not change how the ticker must be designed and tested.
A static mock-up is useful before you add motion. Put a representative listing over a typical frame from the loop and inspect it at the actual output size. Check whether the brand mark and listing content remain distinct from bright skies, dark interiors, and busy footage. If the strip only works on one scene, consider changing its background or placement rather than assuming viewers will infer the text.
Add the ticker using the chosen encoder’s workflow
The exact controls depend on the encoder. In OBS, add a Browser Source to the intended scene, choose its hosted URL or local file, set the source viewport dimensions, and position and resize it in the scene. The steps and labels here are OBS-specific; do not treat them as a universal sequence for other encoding software. Consult the chosen encoder’s current documentation for its equivalent way to add a browser or graphics layer.
After adding the source, inspect the scene at full canvas size. Confirm that the ticker is above the video layer and below any element meant to cover it. If the ticker is cropped, first check the browser viewport and then the source transform in the scene. A page may have its own margins or padding, so a source that is correctly positioned can still show unwanted whitespace inside its viewport.
Once the visual scene is composed, connect the encoder to the YouTube broadcast. YouTube’s encoder setup instructions explain the Live Control Room flow and the use of the stream URL and stream key. Keep the key private. For a scheduled stream, check the preview in Live Control Room and use its controls to begin the broadcast when the picture and stream status are ready; do not assume that adding the ticker in OBS publishes it by itself.
A 24/7 channel has an additional operational consideration: the ticker page and the loop must remain in a known state over time. If the content is updated while live, verify that the change appears correctly in the scene. If a browser source refreshes, returns from an error, or reloads an expired page, the audience could see an interruption or a blank strip. Decide who checks the source and what approved fallback scene should be used if it fails.
StreamNeo can remove the need to leave your own computer running for an uploaded video loop, which is useful when the recurring problem is keeping that machine on overnight. The ticker still needs to be prepared as part of the broadcast visuals, and you should verify that the graphics and listing content are present in the finished stream before relying on them.
Check legibility, pace, and screen placement
Read the ticker from a normal viewing distance on a phone as well as on a larger screen. Property details that look comfortable on a desktop monitor can become too small when the live video is viewed in a mobile app. Use a plain typeface, clear contrast, and enough spacing between listing cards that one item does not visually merge into the next.
Check the pace with the actual amount of text. A short locality and price can move more quickly than a longer description without becoming hard to follow. If viewers need to read a listing before it scrolls away, slow the movement or keep the item on screen longer. Do not try to solve an overly fast ticker by packing in smaller text; reduce the copy or split it into a second pass instead.
Screen placement should respect both the video and the YouTube player interface. Keep the ticker away from important property details in the footage and avoid placing critical text at the extreme edges, where different displays or player controls may make it harder to see. Check placement in the actual live preview and a playback view, not only in the OBS canvas. The overlay can be correctly aligned in OBS but still feel cramped once the video is presented in its player.
Use representative scenes when judging contrast. A white ticker over a light wall, a dark strip over a night shot, or a translucent background over moving foliage can each reduce readability. A moderately opaque backing panel often creates more consistent text contrast, but it should not cover more of the property than necessary. Compare the strip against several portions of the loop, not only the opening frame.
If the listing includes a phone number, URL, or other call to action, check that it remains legible for long enough to be useful. A URL that scrolls past in a second is decorative rather than actionable. Consider displaying the brand or destination consistently while the listing details rotate, and make sure the displayed destination is accurate and maintained.
Preview and test the finished loop
Test the full path from ticker asset through encoder to YouTube. A local OBS preview confirms that the source is layered and moving, but it cannot tell you whether the encoded output reaches YouTube as expected or whether the final player presentation is readable. Use a private or otherwise appropriate test broadcast when possible, and check the returned picture on a separate device or account rather than relying only on the production screen.
Include representative movement and audio in the test. YouTube advises testing before starting a live stream and recommends checking upload bitrate with a speed test in its encoder settings guidance. Follow the current encoder recommendations for your chosen resolution and available upload connection; do not assume a single bitrate fits every stream. The same YouTube guidance covers protocol, bitrate, and keyframe recommendations, which should be checked again when configuring the encoder because platform settings can change.
Watch more than one ticker cycle. Confirm that the first item does not start clipped, the last item exits cleanly, and the transition back to the first item does not produce a visible jump or long empty gap. If the listings update, test a change as well: verify that the old item is removed as intended and that the replacement does not overlap or break the layout.
Check stream health during the test and look for problems beyond the overlay. A smooth ticker cannot compensate for a frozen background video, missing audio, or a connection that is repeatedly dropping. If the stream reconnects, verify what viewers see after it returns. The troubleshooting guide for a 24/7 stream that keeps stopping addresses continuity problems in a loop, while this test should confirm your own encoder and scene behave as expected.
If the ticker is a web page, repeat a test after any significant page or feed change. A design update that is harmless in a desktop browser can alter the overlay dimensions or contrast. Keep a record of the tested scene, source, and approved content version so that a later edit does not silently replace the one you checked.
Review listing accuracy before going live
Treat the ticker as public advertising content. Check each property identifier and every visible claim against the authoritative source: location spelling, price, availability, property type, and contact route. Remove or correct an item promptly when you learn it has changed. A continuous loop may repeat outdated information many times, so set a review routine that matches how quickly the listings can change.
Confirm that the person or organisation responsible for each listing has approved the information and any required presentation. This is especially important for photographs, logos, agent contact details, feed data, and terms such as “available” or “under offer”. Requirements vary by market and contract, and the reviewed streaming documentation cannot settle those questions. Ask the relevant provider or rights holder what may be displayed in a public live broadcast and whether notices or attribution are required.
YouTube-native shopping features are separate from a custom ticker. A graphic rendered into an encoder scene is part of the video image; it is not a YouTube product tag or shopping surface. Native features may have their own eligibility and availability conditions, so check YouTube’s current official guidance if you intend to use them. Do not assume that a custom on-video listing strip unlocks those features, or that native shopping tools will supply your ticker’s design and content.
Make the final preflight a content review as well as a technical check. Confirm the scene is the approved version, the listing source is current, the ticker is readable on the test playback, and the stream is connected to the intended YouTube event. Keep a way to hide the ticker or switch to a clean scene if you discover a wrong price or broken feed after going live. That is more useful than leaving incorrect details on screen while you try to repair the source.
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
How do I add a property ticker to an OBS stream?
In OBS, add a Browser Source to the scene and load a hosted ticker page or local HTML file. Set the source viewport, place it above the video layer, and check the result in the scene and YouTube preview. These steps are specific to OBS; another encoder may use different controls.
Does YouTube automatically add a custom property ticker?
No. YouTube receives the completed video from your encoder, and a custom ticker must be rendered into that video scene before it is sent. YouTube-native shopping surfaces are separate features and may depend on eligibility.
Can I show MLS or other property-feed listings in a live loop?
Only after confirming that the applicable feed agreement and rights holder allow this use. Permission to display data on a website does not by itself establish permission for a public broadcast, and rules vary by provider and market. Check the terms and any attribution or notice requirements before publishing.
Should I use a hosted ticker page or a local HTML file?
Use a hosted page when central editing is valuable and you can keep the page and any data source available. A local file can suit a fixed, pre-approved set of listings, but updates must be made on the production machine and tested there. In both cases, keep an approved fallback and review the display after changes.