One badge.
Every client.
Zero exceptions.

Your badge data expires 180 days after your last update, every time you set, switch, or delete a badge, that 180-day timer resets. So as long as you touch the plugin at least occasionally, nothing gets deleted.

If you go longer than that without any changes, your data quietly expires from the backend and you'd need to set your badge up again.

Use Share Badge to export your current active badge (image, name, and all style settings) as a copyable code, it's base64-encoded JSON. Paste someone else's code into Import Badge Code and hit Import Badge to apply their look as your own.

Invalid or corrupted codes will just show an error toast instead of silently failing.

Yes, badge writes (setting, switching, or deleting a badge) are rate-limited server-side. You won't hit it under normal use, it exists to stop abuse/spam, not to get in your way.

Export is capped at 12, since that's also the max number of badge slots you can have saved at once, a pack you make (Make Pack (Copy JSON)) can never contain more than 12 badges anyway.

Import is different: a pack file can technically contain as many badges as you want, but the plugin will only import the first 6 from it. Anything beyond that gets ignored.

Recommended: keep packs you share to 6 badges so people get everything in one import. If you've already got a bigger pack, split it into multiple packs of 6 rather than one large one.

You can save up to 12 badges per account and switch which one is active. This is a server-side limit to keep storage reasonable for everyone, delete an old badge if you're at the cap and want to add a new one.

1. Badge changes are saved server-side and can take a moment to propagate. Try switching channels/reopening your profile. If it still doesn't show, check that your image URL is a direct link ending in .png, .jpg, .jpeg, .gif, or .webp, links to a webpage instead of the raw image file will be rejected.
2. Check whether you have Hide Own Badge toggled on.

That split is expected during an outage. Viewing badges (yours or anyone else's) is a public, unauthenticated read, so it keeps working even if other parts of the backend are having issues. Verifying, setting, switching, or deleting a badge all require a fresh Discord OAuth "verify" round-trip first, if that flow (or the write path behind it) is degraded, those actions will fail even though reads look totally normal.

Check the status page, if Discord Verify or KV Writes is showing degraded/failing there, that's the cause, and it's already a known, tracked issue rather than something wrong on your end. Nothing you do locally (reinstalling the plugin, re-verifying repeatedly, etc.) will fix it, it needs to clear on the backend first, so it's best to just wait it out and try again once that subsystem goes back to operational.