To put TipeeeStream donation alerts on a live broadcast, configure a widget in Tipeee’s Streaming section, copy its widget URL, then add that URL as a browser source in OBS or Streamlabs. Position the source in your scene, use Tipeee’s alert configuration to preview it, and refresh the source after you edit the widget.
The widget URL is a configuration URL for the streaming software, not a general public page to share. A preview animation can help you check the visual setup, but it does not prove that a payment, payout or live alert has been processed end to end.
Open TipeeeStream’s Streaming section
Sign in to TipeeeStream and open the Streaming section from the page menu. Choose the widget you want to configure. The exact options presented can depend on what is available in your account, so use the controls you can see rather than assuming every documented feature is enabled for every creator or country.
Tipeee’s widget instructions describe the basic route: configure the widget, copy the URL supplied for it, then place that URL in a browser source in your broadcast software. This is the relevant path whether you are preparing a devotional stream, a music channel or a local programme; the alert sits over your video scene, while the broadcast itself still needs to be running through your usual streaming setup.
Before working on the appearance, decide what the alert should communicate. A short message and a restrained animation may be easier to read over a song or a talking segment than a large block that covers faces, lyrics or captions. If you plan to use spoken messages, think through how viewer-submitted text will sound on air and review the available controls before enabling it. The separate guide to text-to-speech on donation alerts is useful if speech is part of the presentation you want.
Treat settings as presentation and behaviour choices, not a promise of donations. Tipeee’s feature page lists options such as payment-method settings, minimum or suggested amounts, custom messages, file attachments, sounds, animations, text-to-speech, goals, counters and layouts. Those are listed platform features, not evidence that each method or feature is enabled for every account. Check the options and applicable payment terms in your own account before you invite viewers to contribute.
If the broadcast is primarily a continuous prerecorded loop, keep the alert work separate from the video-playback system. The article on tools for streaming prerecorded video continuously covers that broader task; this setup only addresses the donation overlay inside the scene.
Configure the donation widget
Choose the widget’s appearance and behaviour in Tipeee before copying its URL. Work through the controls deliberately: select a layout, decide what text should appear, and set any sound or animation options you intend to use. Avoid changing several things at once while the source is already in OBS or Streamlabs, because that makes it harder to tell whether a later visual change came from the widget settings, source dimensions or scene layout.
A useful first pass is to make the alert recognisable without allowing it to dominate the programme. Consider where the message will sit, how long it remains visible according to the controls available, and whether the sound would interrupt the content. For a bhajan stream, for example, an alert sound that competes with the music may be more disruptive than a quiet visual card. For a local news loop, text may need to remain clear of the ticker or lower-third area. These are scene-design decisions; Tipeee’s controls determine which choices are available to you.
Payment and message settings deserve a separate check from appearance. A suggested contribution is not the same as a required minimum, and a viewer’s payment is not guaranteed by the wording on an alert. Review the actual account settings and payment terms, including whether a method is available to the people you expect to watch. Do not describe an ordinary tip as a tax-deductible charitable gift. If you are collecting for a cause, make clear who receives the payment and how it will be handled; Twitch’s charitable donations guidance distinguishes a payment to a streamer who later gives money to charity from a donation processed through Twitch’s Charity tool.
Save or apply the widget configuration as the Tipeee interface requires, then look for the dedicated widget URL field. Do not assume the URL is a public donation page: its documented purpose in this workflow is to connect the configured widget to streaming software. Use a separate, clearly identified donation route if you intend to share a page with viewers, and verify that route within your own account.
Copy the widget URL carefully
Use the page’s Copy button for the widget URL after configuration. This small step avoids selecting only part of a long address or copying text from the wrong field. If you need to move between windows, paste the copied address into the URL field of the browser source rather than placing it in a public post, chat message or on-screen text.
Keep a private note of which source uses which widget if you have several scenes or alerts. A devotional channel might maintain a quiet overlay for a prayer scene and a separate presentation for announcements. Naming sources clearly later helps you distinguish them in the scene list. Do not circulate the widget URL as though it were the public donation destination; it is the configuration address used by the browser source.
If copying seems to have failed, return to the widget’s own page and copy again rather than reconstructing the address by hand. A typo or truncated URL can leave the source blank or show an error, while the configuration in Tipeee may still look correct. Keeping the widget page open until the source has loaded makes it easier to confirm that you added the intended URL.
Add a browser source in OBS or Streamlabs
In OBS, open the Sources panel, select the plus button, choose Browser, create and name the source, paste the widget URL into its URL field, and confirm. In Streamlabs, open Sources, select the plus button, choose Browser Source, create and name it, paste in the same type of widget URL, and confirm. Labels in the software can vary slightly by version, but the key is to create a browser source rather than a media-file source or a text source.
Name the source for its purpose, such as “Tipeee alert,” rather than leaving a generic label. Clear names matter when a scene contains a camera, logo, background video, captions and several browser elements. If you later need to refresh or hide the alert, you can identify the correct source without guessing.
Once added, check that the source is enabled and belongs to the scene you intend to broadcast. A browser source in a different scene will not appear simply because it exists elsewhere in the project. If you use multiple scenes, decide whether the alert should be present in all of them and add or reuse sources accordingly, taking care not to show duplicate alerts from overlapping sources.
Use your existing broadcast software for this step; there is no need to switch platforms solely to add the widget. OBS and Streamlabs follow the same essential browser-source idea, while their panels and menus differ. If your wider setup depends on a local computer staying on for a continuous broadcast, the practical considerations are different from adding an overlay; see the guide to cloud services for a 24/7 YouTube music stream. StreamNeo can remove the specific overnight burden of keeping your own computer on by running an uploaded video as a YouTube live stream, but it does not change the Tipeee widget setup described here.
Position and size the widget in your scene
Select the browser source in the preview so its outline and handles appear. Drag it to the intended part of the frame, then use the edge handles to resize it. Check the result against the actual scene composition, not just an empty canvas: a source that looks well placed over a blank background may cover a face, title, lyrics or ticker once the complete scene is visible.
Use a representative scene to choose the location. For a music or ambience channel, keep the alert away from the main visual focus and any captions. For a presenter, avoid the area where the person’s face or name graphic appears. If your video has important information near the edges, leave room for the alert rather than covering it. The right size is one where the message can be read at normal viewing size without taking over the broadcast.
If the source appears too large or too small, adjust it in the preview rather than repeatedly changing the widget URL. Position and size are scene-level adjustments in the broadcast software; the URL connects to the configured widget. Keeping those responsibilities distinct makes troubleshooting easier: use Tipeee for the widget’s content and appearance controls, and OBS or Streamlabs for placement in the scene.
Check that the full alert box remains inside the canvas. A source partly beyond the frame may be clipped on the broadcast even if the preview makes the position look close enough. Where the software’s preview can be scaled, use the scene boundaries as your reference rather than the physical monitor edges. After sizing, leave enough clear space for longer messages if your configuration allows custom text, because a short test message may not show how a longer one will fit.
Trigger a test alert and refresh after edits
To preview an alert using Tipeee’s documented workflow, open its alert configuration and select “Restart animation.” The alert may first appear as a coloured rectangle in the software preview. Use this to inspect whether the source is loading and whether its position is sensible. A preview animation is not a completed test of a real payment, payout or alert delivery to viewers.
If the preview does not appear, first check simple causes: the correct source is in the current scene, it is visible, the URL was pasted into the URL field, and the source is not hidden behind another element. Revisit Tipeee’s configuration to confirm that you copied the URL for the widget you actually edited. Avoid interpreting a missing preview as evidence about payment processing; the preview checks the visual connection, not the entire donation journey.
After changing a widget in Tipeee, refresh the corresponding source in your broadcast software so it loads the most recent version. In OBS, select the source and use Refresh. In Streamlabs, open the source gear and choose “Refresh cache of current page.” Then trigger the animation preview again and inspect the result. This explicit refresh is easy to forget because the source can remain visible with an older version of the widget.
Make one edit at a time when the layout is not behaving as expected. For example, change the text or animation in Tipeee, refresh the source, and observe the result before adjusting the source size in the preview. If you alter both the widget design and the browser-source dimensions together, it is less clear which change fixed or caused the problem. For a dependable routine, check the overlay before going live and repeat the refresh-and-preview sequence after any later widget edit.
Keep donation expectations and integrations clear
A configured alert is only one part of a donation setup. The viewer needs an appropriate way to contribute, and the account must support the relevant payment method and terms. An animation preview only demonstrates a visual state in the software; it does not confirm that a viewer can pay, that a payment will be accepted, or that funds will be paid out on a particular schedule. Verify the current details in Tipeee’s own account pages before announcing amounts or payment routes.
Tipeee’s news page describes a YouTube Superchat route involving YouTube as the “Master-Account” and the Superchat tab in Alert Box. The page also includes older announcements and technical notes, so treat this as a path to inspect in your dashboard rather than a promise that the integration remains available to every account. YouTube features and account eligibility can change; confirm current status in the relevant settings and official guidance before relying on it.
The standard browser-source steps do not require API access. Tipeee’s developer documentation describes more advanced ways to read event data or trigger events, including API and socket-related routes. Those are for custom integrations, not a necessary extension of the straightforward OBS or Streamlabs setup. If you are not building your own integration, leave those technical paths alone and use the widget interface.
Keep any public explanation to viewers precise. If you share a donation page, verify that it is intended for viewers and not the browser-source configuration URL. State what the contribution supports without implying that a particular contribution guarantees a particular alert or result. When the stream itself is an always-on YouTube broadcast, treat the overlay as one scene element among the other operational checks: the video source, audio, stream status and scene selection still need their own review. The guide to choosing a recurring YouTube stream key addresses a separate part of that broadcast preparation.
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
Is the Tipeee widget URL a donation page to share?
No. In the documented setup it is the URL copied from the configured widget and pasted into a browser source in OBS or Streamlabs. Do not publish it as though it were a public contribution page; verify and share the appropriate viewer-facing route from your account instead.
Does “Restart animation” test a real donation?
It previews the alert animation in the broadcasting software. It does not demonstrate that a payment was made, that a payout will occur or that an alert will reach viewers during a live broadcast. Treat it as a visual setup check only.
Why do widget edits not show up in OBS or Streamlabs?
The browser source may still be showing a cached or earlier version. Refresh the source in OBS, or use the source gear and “Refresh cache of current page” in Streamlabs, then preview the animation again.
Do I need API access for the basic widget?
No. The documented path is to configure the widget, copy its URL and add a browser source. API and socket documentation describes advanced integration work and is not required for this setup.