Work through these steps in order. The most common issues have simple fixes — wrong Beyond20 configuration accounts for the majority of "rolls not showing up" reports we receive.
Before deep-diving, confirm all five of these are true. Most issues come down to one of them:
https://www.owlbear.rodeo/* is in Beyond20's custom domains list (the single most common missed step)If any of these are false, fix it first before reading further. Most issues are resolved by #2 alone.
Work through these in order. Each check builds on the previous one.
Open your browser's extension manager:
chrome://extensionsedge://extensionsabout:addonsFind Beyond20 in the list and confirm the toggle is ON. If it's not installed, install it first: beyond20.here-for-more.info/install.
Open your D&D Beyond character sheet and click the Beyond20 icon in the toolbar. Navigate to More Options → Advanced Options and look for the "List of custom domains to load Beyond20" field. It must contain:
https://www.owlbear.rodeo/*
Without this entry, Beyond20 won't activate on Owlbear Rodeo pages, which means Owl20 receives no roll data to bridge. Add it, save, and refresh both tabs.
In your browser's extension manager, find Owl20 and confirm it's enabled. If it was recently installed, try disabling and re-enabling it. Then refresh your Owlbear Rodeo tab.
As a player, you can't enable the Owlbear Rodeo-side extension — only the DM can. The DM needs to:
If the DM hasn't set this up yet, point them to the DM Setup Guide.
Close your D&D Beyond tab entirely and reopen it. Then close your Owlbear Rodeo tab and reopen it. This forces both extensions to reinitialize from scratch. Don't just press F5 — fully close and reopen the tabs.
On your Owlbear Rodeo tab, press F12 to open Developer Tools, click the Console tab, and look for messages starting with Owl20:.
Healthy output looks like:
Owl20: Initializing data bridgeOwl20: Found iframe to owl20-owlbearOwl20: Listening for Beyond20 roll eventsIf you see no Owl20 messages: the extension isn't loading on this page. Check that it's enabled in your browser extension manager and that you're on an owlbear.rodeo URL (not a local file or different domain).
If you see red error messages: copy the error text and search the FAQ or post it in the GitHub Issues.
Aggressive ad blockers (uBlock Origin with strict settings, Privacy Badger, etc.) can block the extension's cross-origin messaging. Try temporarily disabling all other browser extensions while on both owlbear.rodeo and dndbeyond.com. If rolls start working with other extensions disabled, add an exception for both domains in your ad blocker settings.
If Owl20 doesn't appear in your browser extension manager or won't install:
Owl20 supports Chrome, Edge, and Firefox. It will also work on any Chromium-based browser (like Brave or Opera) that supports Manifest V3 extensions.
If you're using Safari, Internet Explorer, or an older pre-Manifest V3 browser, Owl20 is not supported on those platforms.
Manifest V3 extensions require a relatively recent browser version. Check for updates:
chrome://settings/helpedge://settings/helpOwl20 needs access to owlbear.rodeo domains. In your browser extension manager, click on Owl20 and review its site permissions. If access was denied or restricted, grant it.
Close all browser windows completely (not just tabs) and reopen. This clears cached extension states. On Windows, make sure the browser isn't still running in the system tray.
Chrome is the most tested browser for Owl20. If you're having issues on Chrome specifically:
Edge uses the same Manifest V3 system as Chrome, so compatibility is generally the same. One Edge-specific note:
owlbear.rodeo to Edge's "Sites that can bypass Enhanced Security" exceptions.Firefox uses a slightly different extension model. If Owl20 isn't working in Firefox:
user.js or use Firefox Hardened, try with a fresh profile to isolate the issue.Owl20 can be installed on Opera via the Chrome Web Store using the "Install Chrome Extensions" option. Opera-specific issue: Opera's integrated ad blocker may need to be disabled on both owlbear.rodeo and dndbeyond.com.
Owl20 does not support mobile browsers. Browser extensions are not available on iOS or Android. Both D&D Beyond and Owlbear Rodeo must be accessed from a desktop browser.
If rolls sometimes appear and sometimes don't, or there's a noticeable delay:
If you had Owlbear Rodeo open before the DM enabled the extension, you may need to refresh your tab. The extension initializes when the page loads, not when it's toggled on mid-session.
If you have multiple Owlbear Rodeo tabs open simultaneously, Owl20 runs in each one independently. Rolls will appear in the tab where the Owl20 OBR extension is active. Close extra tabs and work from a single Owlbear Rodeo tab.
If your browser has many tabs open and is under memory pressure, extension messaging can be delayed. Closing unused tabs may help.
If you've worked through all the above and still can't get Owl20 working:
The FAQ page covers 33 specific questions including browser support details, permission explanations, and more niche setup scenarios.
If you think you've found a bug, open an issue at github.com/uberdragon/owl20/issues. When reporting, include:
Owl20: messages from the browser console (F12 → Console)Join the Starry Shores Discord and ask for DM UberDragon or DM Sparks. We're both active in the server and usually respond within a day. We both run this setup ourselves every session, so we can work through most issues quickly.
The more information you bring to the conversation — browser, console output, what step fails — the faster we can help.