A maintainable way to show a clock and weather over a 24/7 nature stream is to load a combined overlay in OBS as a Browser Source. The page may be a hosted URL or a local HTML file; live weather still needs a page or service that supplies current data.
OBS does not itself provide live weather data, and a normal Text Source is not established as an automatically updating clock. Choose an overlay that fits your comfort with maintenance, then check its time zone, location, readability and behaviour after a reload before leaving it on air.
Choose a clock and weather overlay source
Start by deciding whether you need a clock, weather, or both. A clock can be useful even when the nature footage carries no other information: viewers in different time zones can tell when they have tuned in, and a local sunrise or birdsong scene can be labelled with the place it represents. Weather is more demanding because a current temperature or condition has to come from a data source, not merely from the video software.
OBS's Browser Source documentation describes loading a page from a URL or a local file. That gives you several practical routes. A hosted overlay can be quick to add, but it relies on the overlay host and your internet connection. A local HTML page keeps the presentation file on your streaming computer, but if that page requests live weather from an API, it still relies on the network, the provider, and any required key or account. A plugin may bundle presentation controls, but it adds a compatibility and maintenance decision.
| Approach | Useful when | What it depends on | Main trade-off |
|---|---|---|---|
| Local HTML clock in Browser Source | You need a clock without live weather | The local page and the computer's clock | Few outside dependencies, but you choose and maintain the page |
| Local weather page in Browser Source | You want control over a combined display | Local file, network access, and the weather provider; some examples need an API key | Configurable, but weather can stop while the page or data service is unavailable |
| Weather plugin | You prefer a packaged setup or theme | Plugin compatibility, permissions and its data source | May reduce page editing, but needs checking against your OBS version and ongoing maintenance |
| Hosted overlay URL | You want to avoid keeping HTML files yourself | Overlay host and internet access | Simple to enter, but the host must remain available |
These are categories, not endorsements of a particular provider. Community examples show local HTML pages configured with weather services, location and units, but those examples do not establish current API terms, quotas or long-term availability. Check the provider's current documentation before depending on its data in a continuous broadcast. An implementation built for a hobby test may not be suitable for unattended use without checking how it handles failed requests or expired credentials.
If you only want a clock, do not add an API-dependent weather widget simply because it looks convenient. A locally loaded clock page can avoid the weather service dependency. Conversely, if viewers need current conditions, a decorative label such as “rainy” embedded in static text is not live weather. Keep the distinction visible in your design and maintenance plan.
The overlay should suit the stream rather than dominate it. A birdsong channel may need only local time and a concise temperature; a local nature reserve stream may need a location label so viewers know which area the conditions describe. For ideas about the scene itself, see how to set up a 24/7 birdsong ambience stream on YouTube in India. That is a useful companion topic, but it does not remove the need to configure this overlay's own data source.
Add a Browser Source in OBS
Open the scene that contains your nature footage and use the Sources dock to add a Browser Source. Give it a name you can recognise later, such as “Clock and weather”. A descriptive name matters when a scene accumulates footage, audio, labels and overlays; it is easier to troubleshoot a named source than several entries called “Browser”.
For a hosted overlay, enter its URL in the source properties. For a local page, select the local file using the file option and browse to the HTML page. OBS's Browser Source guide covers the source's URL and local-file modes. Keep track of where a local file lives and avoid moving or renaming it casually: OBS needs to be able to load the same page after a restart. If another person maintains the channel, document that path for them.
Set the Browser Source width and height to match the intended canvas of the page or the overlay area it is designed to occupy. OBS's default Browser Source viewport is 800 by 600 pixels, so it may not match a typical video canvas or a compact panel. Treat the dimensions as the page's working area, not as a guarantee that the content will fill it well. If the widget is designed for a narrow strip and you give it a large viewport, empty space or unexpected scaling may result.
If the page is local HTML, test it in the OBS preview rather than assuming it behaves exactly like a normal browser tab. Some pages depend on web fonts, scripts, remote images or API requests. A page that looks correct while you are building it can still render differently in OBS if a resource fails to load. Keep a copy of the working file and note any required settings, such as a weather key, city, unit selection or time format.
A local file does not mean the whole overlay is offline. The HTML can be on the computer while its weather values come from the internet. If the network drops, the clock may continue while the weather becomes stale or disappears. That distinction is useful when deciding whether you can leave the setup unattended overnight.
Set its dimensions and position
Use the preview to size and place the overlay. Select the Browser Source and drag its corners or use the transform controls to position it within the video frame. First establish the source's intended canvas dimensions in its properties, then adjust its position and scale in the scene. If the overlay is clipped, check the page's own dimensions and the Browser Source viewport before repeatedly stretching it; scaling a poorly sized page can make text too small or distort spacing.
Choose a corner or edge where the footage is relatively calm. A clock over a bright patch of moving water can be harder to read than the same panel over dark foliage, while a panel placed across a bird feeder or the horizon hides the subject viewers came to watch. Preview several moments of the loop, not just one still frame. Clouds, branches, birds and changes in light can make a placement that looked clear at first less suitable later.
Leave a margin between the panel and the edge of the frame. Tight edge placement can feel cramped and risks making text look cut off on different screens or after a crop. There is no single correct margin for every overlay: use the preview at the output resolution you plan to stream, then check the result at a smaller viewing size as well. On a phone-sized preview, a panel that is legible on your desktop may become too dense.
Avoid making the Browser Source larger just to make its text larger if that also creates a large opaque block. If the widget allows styling, change its typography or layout first. If it does not, try a more compact panel or a different overlay rather than hiding more of the scenery. Make one adjustment at a time and compare how much footage the panel covers.
Layer it above the nature footage
In OBS, source order determines what appears in front. The OBS Sources Guide explains that a source higher in the list appears above sources lower in the list. Place the clock and weather Browser Source above the nature video source; if it is underneath, the panel may be loaded correctly but hidden behind the footage.
A sensible order might put background colour or a scene base at the bottom, nature footage above that, and the clock/weather panel above the video. Other items, such as a channel logo, can be arranged according to what should be in front. The exact order depends on your scene, but test it by toggling the visibility icon beside sources and confirming that the panel appears and disappears as expected.
If you use nested scenes or scene groups, check which scene actually owns the footage and overlay. It is easy to add the panel to a scene that is not the one being broadcast, or to place it below a source that covers the full frame. Verify the final output in OBS's preview and, where practical, in a private or otherwise non-public test before using it on the live channel.
Think of the overlay as part of the composition, not an independent label. A second logo, chat panel or alert can compete with the clock for the same quiet corner. If your stream already has a persistent graphic, decide which information viewers need most and simplify the rest. The aim is to make the scene informative without turning a calm nature loop into a dashboard.
Keep time, location and weather legible
Use a hierarchy: time should be easy to scan, location should identify whose local conditions are shown, and weather detail should remain concise. A city name and temperature can often do more than a sentence of changing description. If you show a time zone, make sure it matches the place the channel is presenting. A clock that follows the streaming computer's local time can be misleading if the channel represents a different region.
Check both the time zone and 12- or 24-hour format in the overlay's settings. Then compare the displayed time with a trusted clock for the intended location. Do not assume that a page uses the same convention as your computer simply because it displays a plausible time. If viewers are likely to be in India but the nature scene represents another location, label that location clearly rather than implying the weather is local to the viewer.
For temperature, choose units that fit the audience and make the unit explicit. A bare number can be ambiguous. If the widget offers conditions and temperature, avoid squeezing in extra detail simply because it is available. Small text that cannot be read on a phone is not useful information. Prefer a few clearly separated elements over a row of tiny values.
Contrast matters more than decorative styling. White text may disappear against pale sky or mist; dark text can vanish over shaded leaves. A small translucent backing plate, subtle outline or restrained shadow can separate the panel from changing footage. Use enough opacity to preserve legibility without covering a large portion of the scene. These are design choices rather than official OBS presets, so judge them against your actual footage.
Keep the panel visually stable. If a weather description changes from a short word to a longer phrase, it should not overlap the time or force the layout to jump across the screen. Choose a widget that wraps or allocates space sensibly, or use a compact condition indicator if the provider and page support one. Watch the layout through changes in weather and lighting; the most readable state is not always the default state.
For a channel built around long, unhurried footage, consistency is part of the viewing experience. An overlay that flickers, changes size or competes with the focal point can distract even if every value is correct. If you are setting up the broader channel as well, the guide to a 24/7 meditation music live stream on YouTube offers a related example of planning a continuous scene. Keep any overlay modest enough that the underlying ambience still carries the stream.
Test updates and recovery for continuous use
Test the clock and weather separately. Confirm that the clock advances and uses the intended zone and format. Confirm that the weather location and units are correct, then observe whether the displayed condition changes or refreshes according to the page's own design. Do not infer a provider's refresh schedule from how quickly a page initially loads. Community samples use different approaches; their behaviour is not a guarantee for another widget or for current provider terms.
OBS Browser Source properties include controls related to refreshing the cache and refreshing when a scene becomes active. There is also a “Shutdown source when not visible” option, which unloads the page while it is hidden. For a persistent nature scene where the overlay should keep running, leave it visible and consider whether unloading when hidden is appropriate. The right setting depends on how you switch scenes and how the page recovers when loaded again.
Test an OBS restart and a network interruption before trusting the setup to run unattended. Watch whether the page returns, whether the clock resumes, and whether weather data eventually comes back. This is a practical check, not proof that a third-party host or API will remain available. If a remote URL is unavailable, its page may not render. If local HTML is available but its weather API is not, the clock may still work while weather information does not.
Prepare a fallback that does not misrepresent stale data. You might choose a clock-only layout, a static location label, or no weather panel until the data returns. If your chosen widget cannot hide or replace weather when its request fails, decide whether a simple clock is preferable to leaving an old temperature on screen. A stale current-condition display can be more confusing than a temporarily absent one.
For a 24/7 channel, the overlay is only one part of continuity. OBS must remain open, the stream connection must recover, and the source itself must render as expected. If you are also diagnosing dropped connections, see how to configure OBS reconnect delay for a YouTube loop on Indian broadband. Reconnect settings address a different failure mode from a weather page failing, so test both rather than treating one as a fix for the other.
Keep a short maintenance note beside the scene setup: where the HTML file is, which location and units it uses, and what external account or service it depends on. Do not store sensitive keys in a public note or expose them in a screen capture. Review current provider terms and any plugin compatibility information before relying on them continuously. No overlay choice guarantees uninterrupted weather data.
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
Can OBS Text Source provide an automatically updating clock?
A normal Text Source is not established as an automatically updating clock, so do not rely on static text to keep time for you. Use a clock page in a Browser Source or another implementation that explicitly updates the display, then test it in your scene.
Does OBS provide live weather data?
No. OBS can display a page through Browser Source, but live weather has to come from that page or a separate data service. Check the chosen overlay's location, units, update behaviour and provider requirements.
Should I use a local HTML file or a hosted overlay?
A local file gives you control over the page and avoids relying on an overlay host for the file itself, but API-based weather still needs network access and its provider. A hosted URL can be easier to set up, but it depends on that host being available. Choose according to what you are willing to maintain, then test failure and recovery.
Why is my Browser Source not visible over the footage?
Check that the source is enabled and placed above the nature video in the Sources list. Then confirm that the page loaded and that its dimensions and position place the content inside the canvas. A correctly loaded source can still be hidden behind another full-frame source.