Source Map Stack Trace Resolver
A tool that takes a Source Map v3 file and a stack trace and maps minified locations such as app.min.js:1:24050 back to the original source file, line, and column. When sourcesContent is included, the matching source lines are shown. External maps and sources are never fetched — everything runs in your browser.
Supports a single Source Map v3 (indexed maps with sections are not supported). Stack traces in Chrome/Edge (at fn (url:line:column)) and Firefox/Safari (fn@url:line:column) formats are recognized.
The map has no file field, so every frame is resolved with this map.
Result
Enter a source map and a stack trace to see the original source locations.
How to use
- Paste the .map file contents on the left or load the file.
- Paste a stack trace, such as one recorded in production, on the right.
- Optionally enter the generated JavaScript file name. If omitted, the map's file field is used.
- Each frame shows the original file, line, column, and the matching source. You can copy the result.
About this tool
Production JavaScript is minified, so errors point to places like app.min.js:1:24050, which tells you nothing about the code. With the source map generated at build time, you can map them back to the original source.
Browser stack traces use 1-based lines and columns, while source maps use 0-based columns internally. This tool converts between them to avoid off-by-one errors, with an option for tools that output 0-based columns. Frames that can't be mapped or belong to other files keep their original text with an explanation.
This version supports a single, non-sectioned map; indexed maps with sections aren't supported. Locations can be resolved even without sourcesContent. Your map and stack trace are never sent to a server.
For the map, enter {"version":3,"file":"app.js","sources":["src/main.ts"],"names":[],"mappings":"AAAA"}. Resolve at fn (app.js:1:1) using one-based columns: the result is src/main.ts at line 1, column 1. This map contains positions only, so no original source excerpt is available.
Use a map from the same build as the production file. An older map may still load successfully while producing irrelevant positions. The resolver does not fetch external maps or sources; it compares the material you provide locally.
Frequently asked questions
Which browsers' stack traces are supported?
Chrome and Edge (at fn (url:line:column)) and Firefox and Safari (fn@url:line:column) formats are supported.
The resolved location is off by one.
The column numbering may not match. Browser stack traces are 1-based; switch the setting if your tool outputs 0-based columns.
Can I use it without publishing my source map?
Yes. The map is read only in your browser and never sent to a server.