A donation GIF appears when an alert provider receives a supported tip or donation event and sends its overlay to your streaming scene. Configure the event and GIF with the provider, add its widget to OBS as a Browser Source, then test the whole chain before going live.
OBS displays the alert; it does not process donations or provide alerts itself. The collection method, eligible event types and on-screen presentation are separate parts of the setup, and support can differ by provider and platform.
What you need before setting up an alert
You need a way to receive the payment or platform event, a provider that can turn that event into an alert, streaming software that can display the overlay, and a GIF or other visual asset. These roles may be connected in one provider dashboard, but they are not interchangeable. Uploading a GIF does not create a donation option, and adding an overlay does not make the provider accept payments.
For a typical OBS setup, the provider gives you an alert widget or URL. OBS adds that URL as a Browser Source in the scene you intend to stream. When the provider receives a supported event, its overlay displays the configured alert and OBS includes that source in the output. The OBS Project's alert FAQ describes this third-party overlay approach.
Before configuring anything, decide what event you want viewers to trigger. A provider-handled tip may appear under an event labelled “Tips” or “Donations”; a YouTube Super Chat or membership is a platform-native event and may be configured separately. Do not assume that all money sent by viewers is the same event in every dashboard. If your channel already uses platform features, the overview of ads, Super Chats and memberships on a 24/7 YouTube stream can help distinguish those revenue sources.
Also decide where the alert should appear and how much of the screen it can occupy. A full-screen animation that is readable on a desktop preview may cover captions, lyrics or important text on a phone. For a devotional loop, local news ticker or study stream, a short alert positioned away from the primary content is often easier to live with than a large effect that interrupts the scene.
Choose and connect an alert provider
Choose a provider based on the event you need to detect, the platforms it currently supports, whether it accepts the image format you plan to use, and how straightforward it is to add and test its overlay. The steps below use Streamlabs as a documented example, not as a claim that all providers have the same features. Check the provider’s own current support pages and your dashboard before you build around a particular event.
In Streamlabs’ documented workflow, you sign in, connect the relevant platform account, and open Alert Box settings. The provider needs permission and account access appropriate to the event you want to show. If you want provider-handled tips, confirm that the applicable tip feature is available to your account and region, and complete any setup the provider requests. A connected YouTube account alone does not necessarily mean every type of donation or platform event is enabled.
Keep collection and display clear in your own records. A payment provider may handle the tip while an alert service presents a visual notification. OBS only shows the source; it is not where you configure a donation account. The OBS Project’s donations FAQ explains that OBS Studio does not directly provide donation facilities, while noting that third-party providers or platform fundraiser options may be involved.
Once connected, verify the account name and event selection in the alert dashboard. Do not paste a widget URL into a public document or share it casually: it is a link to your overlay, and anyone who obtains it may be able to view or use it according to the provider’s design. If the provider offers a way to regenerate a widget URL, consult its instructions before treating the URL as a secret credential or rotating it.
A practical comparison is not a universal feature ranking; it is a checklist for the provider and software combination you are considering:
| What to check | Provider-integrated alert source | Provider URL in OBS Browser Source |
|---|---|---|
| Where you choose the event | In the provider’s alert settings | Still in the provider’s alert settings |
| How it appears in the scene | Add the provider’s source or widget using the documented workflow | Paste the provider’s widget URL into a Browser Source |
| What OBS does | Displays the configured alert source | Displays the configured alert source |
| GIF and event support | Depends on the provider and integration | Depends on the provider and integration |
| Test method | Use the provider’s preview or test controls | Use the provider’s preview or test controls, then check the OBS scene |
This distinction matters if you are comparing an integrated desktop app with OBS. A built-in source may take fewer steps to add, but the alert still depends on provider-side event and asset settings. A Browser Source is a general way to display web content in OBS; it does not make unsupported event types available. For a wider look at software choices for continuous broadcasts, see OBS versus FFmpeg for 24/7 YouTube streaming.
Configure the donation or tip event
In the alert provider, select the event that corresponds to the action you want viewers to take. In Streamlabs’ guide, this is done in Alert Box settings by choosing the platform and event; provider-handled tips are distinct from platform-native events such as YouTube Super Chats. Menu wording can change, so follow the current dashboard rather than relying on a remembered location. Streamlabs’ official alert setup guide documents its own current workflow and reports its last update as July 6, 2026.
Start with one event and one simple alert. Set the message template to show only the details you want on screen, such as a first name and a short thank-you. Consider whether the provider inserts a viewer’s message automatically: if so, review moderation and display controls, because a live overlay puts user-supplied text in front of your audience. Use the provider’s available safeguards and do not assume OBS will filter content from the alert widget.
Some providers let you create different alert variations based on a condition such as a donation amount. In Streamlabs, the documented variation flow includes adding a variation under Tips, setting a condition, customising the alert and saving it. The available conditions depend on the provider, platform and event. Its guide to Alert Box variations covers that provider’s feature; treat it as a specific example rather than a standard shared by all services.
If you create a variation, make its condition unambiguous and test it separately. A default alert can work while a variation is misconfigured, or a variation can take precedence when you did not expect it. Keep the default event available as a fallback until you have confirmed both behaviours in the target scene.
Add the alert to an OBS scene
Open the OBS scene that should display the alert and add the provider’s overlay using the provider’s instructions. For the common browser-overlay method, add a Browser Source and paste the widget URL. The OBS Project describes this as embedding a third-party alert overlay in the stream. Depending on the provider’s workflow, there may instead be an Alert Box source in its desktop application or plugin; use only the route documented for the software you actually run.
Name the source clearly, for example “Donation alerts”, so it is distinguishable from a webcam, ticker or other browser overlay. Place it above the background and below any element that must remain visible, then resize and position it in the canvas. Check the source in the final scene rather than only in a provider preview. If you have separate scenes for a starting screen, main programme and break screen, decide deliberately which should show alerts; a source in one scene does not automatically mean every scene has it.
Keep the overlay’s canvas dimensions and position aligned with the stream layout. If it is too large, a long message may cover lyrics or a news caption. If it is too small, an animated GIF can become difficult to read on mobile. Use a sample alert to judge the visible area and leave room around text, since names and messages can vary in length.
A 24/7 channel needs an additional scene check: confirm that the source is present in the scene that stays live, and that a transition or loop does not hide it unexpectedly. If you are planning a private rehearsal, the guide to sending a private test stream before launching a YouTube music channel covers a useful way to inspect the output before a public launch. A test stream can help you inspect the composition; it does not verify that a real payment has been collected.
Set the GIF and alert behaviour
Choose or upload the visual in the provider’s settings for the selected event. Streamlabs’ guide lists GIF among its supported image formats, along with formats including PNG, JPEG, WebP, WebM and MP4. That is a Streamlabs-specific statement, not a promise that every alert provider accepts the same formats, file sizes or animation behaviour. If your chosen provider rejects the file, check its requirements or use a format it explicitly supports.
Set the display size and position in the provider where those options are available, then inspect the result in OBS. A transparent background can help the animation sit over your programme, but check the edges against both dark and light footage. A GIF that looks clear in an editor may have a solid background, distracting loops or small text that is hard to read at the stream’s output size.
Set duration, text delay, sound, font and animation with the rest of the programme in mind. A short alert is less likely to obscure a song verse or an important line of a news loop. A loud sound can be jarring when the channel is intended for quiet study or background listening. If alerts are part of the channel’s tone, a restrained visual and a brief message usually make the event clear without turning the stream into a different programme.
Preview each combination of image, text and sound. Use a long sample name or message if the provider’s preview allows it, and watch for overflow, cropped text and overlap with existing overlays. Avoid assuming a GIF will scale in the same way as a static image: inspect the actual animation in the scene, including whether its loop restarts or continues according to the provider’s behaviour.
Test the alert before streaming
Use the provider’s preview or test control to send a sample alert through the configured event. Then watch OBS’s programme preview and, if possible, inspect a private output on another device. A provider preview verifies what the provider can render; seeing the alert in OBS verifies that the source is connected and visible in the intended scene. These are related checks, but neither should be treated as proof that a real contribution will be accepted.
Test the default alert first, then test every variation you created. Confirm that the right GIF, text, sound and duration appear for each sample. Check the transition between scenes if alerts should appear in more than one place, and confirm the alert does not sit behind another source. If the provider test succeeds but OBS remains blank, check that the Browser Source has the current widget URL, is not hidden, and belongs to the scene currently on air. Consult the provider’s documentation for source-specific troubleshooting rather than guessing at settings.
Do not use a real donation as your first test unless you have checked how the provider handles the transaction and any applicable fees or refund process. A test button is preferable when available. Keep in mind that a simulated test event may not exercise the entire collection process: it can test display without proving that a viewer’s payment method, account eligibility or platform event will work.
For a long-running channel, do the same quick visual check after making changes to the overlay, provider account or OBS scene. That is particularly useful when you update a loop or move sources around. For broader ongoing checks on a computer-hosted broadcast, the practical notes on monitoring CPU usage during a 24/7 YouTube stream may help you spot resource pressure, though CPU monitoring does not validate the provider’s donation integration.
If the alert needs to remain on screen while your own computer is off, StreamNeo removes the need to keep that computer running for an uploaded-video broadcast by running the YouTube stream from the cloud; you still need to configure the provider and verify that the overlay and event behave as intended for your channel.
Check provider and platform support
Before inviting viewers to use a donation or tip option, confirm that the provider supports the exact event, account and platform combination you intend to use. The word “donation” may refer to a third-party tip, a YouTube fundraiser or another feature, and these do not necessarily share the same alert event. Do not assume that a provider’s support for one platform implies support for the same event on another.
Check the provider’s current documentation for supported integrations, eligible event types, file requirements, available test controls and any account or region constraints. For a YouTube-native feature, check the current YouTube Help or relevant official platform guidance as well as the alert provider’s documentation. This article’s sources establish the OBS and Streamlabs workflows described above, not a complete comparison of all services or a guarantee that any particular feature is available to every channel.
Separate the practical questions before going live: Can viewers use the payment or platform feature? Does the provider receive that event? Is the alert configured for that event? Can OBS display the provider’s overlay in the live scene? Test what you can with preview controls, and check current official pages for the parts that depend on policy, location or account eligibility. No overlay setup can guarantee that a platform will approve or enable a particular monetisation feature.
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 process donations or create donation alerts?
No. OBS Studio displays alert overlays supplied by third-party providers, commonly through a Browser Source, but it does not process donations or supply alerts itself. Configure the event and collection method with the provider or platform that supports it.
Can I use any GIF file for a donation alert?
Not necessarily. File formats and upload requirements vary by provider; Streamlabs documents GIF support, but that does not establish the same support for other services. Check your provider’s current requirements and preview the chosen file in the final OBS scene.
Will a test alert prove that a real donation works?
A test alert is useful for checking the provider’s rendering and whether OBS displays the overlay in the right scene. It may not test whether a real payment or platform-native event can be received. Confirm event and account support separately before telling viewers how to contribute.
Can one alert show tips and YouTube Super Chats?
Only if the provider and your account support those event types and you configure them accordingly. Tips and platform-native events can be separate alert categories, so check the provider’s current integration details and test each one rather than assuming a single setting covers both.