Hi everyone – Joey here.

I wanted to quickly share that BugSplat's default crash POST size limit has been increased to 100 MB! This gives developers even more flexibility when including logs, screenshots, or other attachments in their crash reports.

Why This Matters

Big crashes often bring big problems—ones that need detailed diagnostics to resolve. Whether you’re sending hefty logs, verbose stack traces, or debug files, BugSplat is now even better equipped to handle the data you need to fix those tricky bugs.

Need More Space?

If you have crash reports that exceed 100 MB, don’t worry—we’ve got your back. Reach out to our team at support@bugsplat.com, and we’ll work with you to find a solution that fits your needs.

A Quick Reminder on Crash Limits

While 100 MB gives you plenty of room, it’s still important to keep crash report sizes lean:

• Files larger than 100 MB will still be rejected by default.
• Attachments and logs should be optimized whenever possible to avoid rejection.

Curious about why a report might be missing? Check out our Finding Missing Reports guide. It covers common scenarios like rejected crashes due to high volume, repeated crashes, or oversized files.

At BugSplat, we’re all about giving you the tools to fix crashes fast. If you’ve got questions or ideas on how we can make crash reporting even better, don’t hesitate to drop us a note!

Cheers,
Joey