Source Map Stack Trace Resolver
Paste Source Map v3 JSON and a minified browser or Node.js error trace to resolve original files, lines, and source code context.
Private by architecture:
All processing is 100% client-side memory. Your data never leaves this browser tab.
1. Source Map v3 (.map JSON)
0 lines • 0 chars 0 sources
2. Minified Stack Trace or line:column
0 frames
Original Source Trace & Code Previews
Load a source map and click Resolve to de-minify the stack trace.
No trace resolved
About This Tool
Source Map Stack Trace Resolver decodes minified runtime error traces back to original TypeScript, JSX, or ES6 source code lines. Paste your production .map file and stack trace to reconstruct readable debug call stacks.
Includes a zero-dependency Base64 VLQ decoder and extracts embedded sourcesContent lines with pinpoint error indicators. Your source maps and crash dumps never leave your local machine.
Key Features
- Hand-Written VLQ Decoder: Implements the full Source Map v3 specification with stateful relative column, line, and source file index calculation.
- Multi-Engine Trace Support: Parses Chrome/V8, Firefox/SpiderMonkey, Safari/JavaScriptCore, Node.js traces, and single line:col coordinates.
- Embedded Source Snippet Viewer: Highlights the exact error line and column within original source files if sourcesContent is embedded in the map.
- Local In-Memory Execution: Safely inspect proprietary production source maps and customer crash logs without cloud leaks.
Frequently Asked Questions
How do I obtain the source map (.js.map) file?
Most bundlers (Vite, Webpack, esbuild, Rollup, Next.js) generate .js.map files alongside minified bundles during production builds when the sourcemap option is enabled.
Why does the tool show original lines but no code snippet?
A code preview requires the optional sourcesContent array to be included in the source map JSON. If omitted by your bundler, only file names and line/column numbers can be resolved.
Can I resolve a single line and column without a full stack trace?
Yes. Enter either a full multi-line stack trace or simply enter line:col (e.g. 1:1425) into the trace box.
