Source Map Resolver
Maps a minified stack trace back to original files and lines using a source map you supply.
Takes a stack trace from a minified bundle and a `.map` file, and tells you which line of which original source each frame came from. Everything is decoded in the tab — neither the map nor the trace, which often names your internal paths, goes anywhere.
Source map (.map)
Drop a .map file
Read in this tab. Nothing is uploaded.
Minified stack trace
names table. Original source text appears only when the map embeds sourcesContent — a map without it knows positions, not code. Frame lines that do not parse pass through unchanged.How to use it
Get the map
Either the `.map` file itself, or the `data:` URI from a `sourceMappingURL` comment at the bottom of the bundle. Both paste in here.
Paste the stack trace
Straight out of an error report — the whole thing, `Error:` line included. Frames that do not parse pass through unchanged rather than disappearing.
Read the original positions
Each frame gets its source file, line, column and — where the map’s `names` table has it — the original function name. Copy the whole remapped trace with one button.
Common questions
Why is there no source line shown?
Because the map does not embed `sourcesContent`. A map without it knows where things were, not what was written there — the stat under the map says whether yours has it. Build with `sourcemap: true` rather than a paths-only setting if you want the code.
A frame says "no mapping at this position".
The column in that frame falls outside any mapping segment. It usually means the map is for a different build of the file than the one that threw — a deploy that shipped new code with an old map, or a CDN serving a cached bundle.
Is it safe to paste a production source map here?
Nothing leaves the tab — the VLQ decoding and the lookup are done in your browser. Worth remembering that a map with `sourcesContent` contains your entire original source, so where you paste it matters in general, even though it does not here.
Which source map version does it read?
v3, the only one anyone emits. Index maps — the `sections` form used for very large bundles — are not supported; feed the section map that covers your frame instead.
Feed it from
JavaScript Beautifier & Minifier
Strips comments and whitespace from JavaScript or TypeScript without renaming anything, and re-indents a minified bundle so it can be read again.
JSON Formatter & Validator
Pretty-prints, minifies and validates JSON, pointing at the exact line and column of a syntax error.
YAML Formatter & Validator
Re-indents YAML consistently, validates it, and flags the tab and anchor mistakes that break parsers.
TOML Formatter & Validator
Formats and validates TOML, normalising table ordering and inline-table style.
Next
These accept what this tool produces, so the result can go straight in.
HAR Viewer & Sanitiser
Opens a HAR capture as a waterfall and strips cookies, auth headers and tokens before you share it.
Hex Viewer
Shows any file as an offset/hex/ASCII dump, identifies the magic bytes and highlights a search hit.
JavaScript Beautifier & Minifier
Strips comments and whitespace from JavaScript or TypeScript without renaming anything, and re-indents a minified bundle so it can be read again.
Base64 Encoder & Decoder
Encodes and decodes Base64 and Base64URL for text or files, handling UTF-8 correctly.
curl to Code
Converts a curl command into fetch, axios, Python requests, Go, PHP or PowerShell.
Text Hash
Computes MD5, SHA-1, SHA-256, SHA-384, SHA-512 and CRC-32 of a string, with an uppercase and Base64 output option.