Welcome

BugSplat is the developer's toolbox for finding, understanding, and fixing crashes. Start here to integrate crash reporting and see your first report in minutes.

When your application crashes in the field, BugSplat captures what you need to understand it: a symbolicated call stack, the runtime environment, and the custom attributes you attach, all presented in a familiar debugger view. You can triage a production crash as if it happened on your own machine, ship more stable software, and spend less time supporting it.

🚀 Start here

The fastest way to see BugSplat in action is to post a sample crash, no code required. It takes about five minutes.

🚀Post Your First Crash in Five Minutes

Ready to wire up your own application? The Full Setup Guide walks you through it: sign up, create a database, integrate your platform, and verify your first real crash.

👀Full Setup Guide

💻 Integrate your platform

Pick your platform and follow its SDK guide. (Each guide assumes you've already created a database, which takes about 30 seconds.)

💻Desktop Software🎮Game Development📱Mobile Apps🕸️Web

🛠️ Fix a problem

Crashes not showing up, or arriving without symbols? Start with Troubleshooting.

Troubleshooting

• My crash isn't showing up

• My crashes are missing symbols, function names, or line numbers

🔌 API Reference

Automate BugSplat and pull your crash data programmatically.

Using the API

📖 Using the app

Once crashes are flowing, learn to triage them, group them, and route them to your team.

Using the AppAlerts & Issue TrackersProduction

🍎 Learn the concepts

New to crash reporting, or want a reference for the terms and workflows?

BugSplat TerminologyHow-TosFAQs

🏢 Admin & billing

BillingAccount

🐛 About BugSplat

What is BugSplat?Who is BugSplat?

---

Stuck or have a question? Email [e-mail], use the in-app chat, or ping us on Discord. You can also search these docs from the bar in the top right.