Capture Unity logs
with one tap
Snapshots bundle Unity logs, screenshots, and device metadata into shareable links. QA captures the moment; devs get the full story. No USB cables, no ADB logcat, no Xcode console.
Typical problems capturing Unity logs on devices
Complex setup and cables
Android requires ADB setup, USB cables, and manual logcat commands. iOS needs Xcode connections and device log navigation. QAs skip logging when setup is too complex.
Missing context
Single exceptions lack the full story. Screenshots live in chat; logs sit elsewhere; device info is forgotten. Teams struggle to piece together what happened.
Device-only bugs
Issues reproduce only on devices. QA can't access logcat or Xcode. Debugging stalls because logs aren't captured when bugs appear.
Sharing friction
Email attachments hit size limits. Logs and screenshots travel separately. Version confusion slows triage. Teams waste time requesting missing details.
One link - full story
Jahro captures Unity logs, screenshots, and device metadata automatically. QA shares a single link to snapshot — devs open it and see everything in order.
Everything captured in snapshots
Shareable snapshots with complete context
When to use:
• device-only bugs
• QA→dev handoff
• playtests
• external QA vendors
• rc builds testing
Analyze Unity logs session with filters and search
When to use:
• diagnosing failures
• tracing execution flow
• reviewing command history
• device-specific bugs
Automatic streaming from Unity game build
When to use:
• non-technical testers
• fatal exception tracking
• playtests
• device testing
Share to your team in one click
When to use:
• understanding environment differences
• tracking device-specific issues
• version compatibility checks
How Unity game teams use snapshots
Dev-QA
QA reproduces Unity bugs on mobile devices and starts a snapshot. Devs see Unity logs, screenshots, device info, and game state—no back-and-forth needed.
Distributed Unity teams
External QA vendors and remote testers share consistent Unity debugging context with zero setup. No USB cables or Xcode access required.
Production Unity debugging
Capture device-only Unity crashes and share snapshots for team review. Stream sessions live or record locally and upload later. Works on live builds without rebuilds.
Get Support. Share Feedback.
Join Discord CommunityWhat your Unity game team gains
Faster triage
One link with full Unity context. Fewer Slack messages; quicker bug fixes on mobile devices.
Less rework
Reduce Unity rebuilds and QA reruns. Capture device bugs and share context in one place.
Clear ownership
Every Unity bug report contains logs, screenshots, device metadata, and game state.
Complete context
Unity logs + screenshots + device metadata show the full story behind the crash or bug.
Reviews
"So we're doing internal playtests with the publisher. They play, and we just watch everything from our end. it's kinda wild."
"way easier than emailing logs from test builds."
"qa uploads a snapshot. I get logs, build version, platform and even a screenshot"
"used to take me ~15 min to pull logs from device. now I get them with full context in seconds. snapshot is my new best friend."
Start capturing Unity bugs with one tap
Add via Unity Package Manager and start capturing complete debugging context in minutes. Works on Android, iOS, and all Unity platforms.