What bundlers generate source maps?

Source maps are generated by webpack, Vite, Rollup, esbuild, Parcel, and other modern build tools. Make sure sourceMap: true is configured in your production build. Most bundlers generate Source Map v3 format.

Why are some frames still showing as unmatched?

Unmatched frames occur when no matching source map was uploaded. Production bundles often have separate source maps for app code and vendor/dependency code. Upload all relevant .map files from your build output.

Can I use this without uploading source maps?

No — source maps are required to resolve minified code back to original source. Without a source map, you'll only see the minified file names, lines, and columns that already exist in the stack trace.

Why don't I see the original function name?

Function names may be mangled if your bundler enabled terser mangling without preserving names. Try enabling 'mangleProperties' or similar options in your build config to preserve function name mappings.

Is this safe for production source maps?

Yes. All processing happens locally in your browser. The source maps are never uploaded to any server. For additional security, you can run this tool offline after loading it once.

Can I resolve stack traces from error monitoring services?

Yes. Paste any minified stack trace from Sentry, Datadog, New Relic, or similar services. Just remove any proprietary formatting and keep the standard frame lines.

What's the difference between this and the Stack Trace Analyzer?

The Stack Trace Analyzer parses and classifies stack traces but doesn't resolve minified frames. The Source Map Explorer takes stack traces a step further by mapping minified coordinates back to original source files using source maps.

DevFlow

Source Map Explorer — Resolve Minified Stack Traces to Original Source

Free online source map explorer and minified error resolver. Paste a production stack trace and upload your source map files to resolve minified file names, line numbers, and column positions back to the original source code. Supports JavaScript and TypeScript source maps v3. Shows original file paths, function names, and surrounding source context for each resolved frame. Groups errors by signature for quick triage. Runs entirely in your browser — your source maps and code never leave your machine.

JavaScript is required to use this interactive tool. Please enable JavaScript in your browser, or use our Source Map Explorer API for programmatic access.

How to Source Map Explorer Online

Upload your source map files (.map or .js.map) by dropping them into the upload zone or clicking to select. You can upload multiple source maps if your bundle uses separate vendor and app maps.
Paste your minified production stack trace into the Stack Trace input field. This should be the raw error output from your production environment with function names like 'a', 'b', 'c' and file paths ending in .js.
Click the Resolve button or press ⌘↵ to resolve all frames. The tool will match each minified frame against your uploaded source maps and display the original source positions.
Review the resolved frames to see original file paths, line numbers, column numbers, and function names. Frames with green checkmarks were successfully resolved.
Expand any frame to see surrounding source context (±3 lines) from your original TypeScript or JavaScript files.
Copy the error signature (e.g., TypeError@src/components/UserList.tsx:24) for quick sharing in bug reports or Slack.
If any frames show as 'unmatched', you may need to upload additional source maps from your build output. Bundled apps often need both app and vendor source maps.

Source Map Explorer Features

Source Map v3 support: works with source maps from webpack, Vite, Rollup, esbuild, terser, and other modern bundlers.
Multi-map resolution: upload multiple source maps and the tool intelligently matches frames to the correct map by file name, basename, or .map extension.
Original position lookup: resolves minified file names, line numbers, and column numbers back to original source coordinates.
Function name restoration: shows original function names when available in the source map.
Source context display: extracts surrounding source lines (±3) from sourcesContent in the source map for debugging context.
Error signature grouping: generates a copyable error signature like 'TypeError@src/utils/api.ts:42' for quick sharing.
Unmatched frame detection: identifies frames where no source map matched so you know what maps to add.
Frame statistics: shows total frames, resolved count, and unmatched count at a glance.
Flexible input: supports drag-and-drop file upload, file picker, or pasting source map JSON directly.
Privacy-first: all source map processing runs entirely in your browser — your source maps never leave your machine.
Stack trace reuse: works alongside the Stack Trace Analyzer — parse first, then resolve with source maps.

Frequently Asked Questions

What bundlers generate source maps?: Source maps are generated by webpack, Vite, Rollup, esbuild, Parcel, and other modern build tools. Make sure sourceMap: true is configured in your production build. Most bundlers generate Source Map v3 format.
Why are some frames still showing as unmatched?: Unmatched frames occur when no matching source map was uploaded. Production bundles often have separate source maps for app code and vendor/dependency code. Upload all relevant .map files from your build output.
Can I use this without uploading source maps?: No — source maps are required to resolve minified code back to original source. Without a source map, you'll only see the minified file names, lines, and columns that already exist in the stack trace.
Why don't I see the original function name?: Function names may be mangled if your bundler enabled terser mangling without preserving names. Try enabling 'mangleProperties' or similar options in your build config to preserve function name mappings.
Is this safe for production source maps?: Yes. All processing happens locally in your browser. The source maps are never uploaded to any server. For additional security, you can run this tool offline after loading it once.
Can I resolve stack traces from error monitoring services?: Yes. Paste any minified stack trace from Sentry, Datadog, New Relic, or similar services. Just remove any proprietary formatting and keep the standard frame lines.
What's the difference between this and the Stack Trace Analyzer?: The Stack Trace Analyzer parses and classifies stack traces but doesn't resolve minified frames. The Source Map Explorer takes stack traces a step further by mapping minified coordinates back to original source files using source maps.

Source Map Explorer — Resolve Minified Stack Traces to Original Source

JavaScript is required to use this interactive tool. Please enable JavaScript in your browser, or use our Source Map Explorer API for programmatic access.

How to Source Map Explorer Online

Upload your source map files (.map or .js.map) by dropping them into the upload zone or clicking to select. You can upload multiple source maps if your bundle uses separate vendor and app maps.
Paste your minified production stack trace into the Stack Trace input field. This should be the raw error output from your production environment with function names like 'a', 'b', 'c' and file paths ending in .js.
Click the Resolve button or press ⌘↵ to resolve all frames. The tool will match each minified frame against your uploaded source maps and display the original source positions.
Review the resolved frames to see original file paths, line numbers, column numbers, and function names. Frames with green checkmarks were successfully resolved.
Expand any frame to see surrounding source context (±3 lines) from your original TypeScript or JavaScript files.
Copy the error signature (e.g., TypeError@src/components/UserList.tsx:24) for quick sharing in bug reports or Slack.
If any frames show as 'unmatched', you may need to upload additional source maps from your build output. Bundled apps often need both app and vendor source maps.

Source Map Explorer Features

Source Map v3 support: works with source maps from webpack, Vite, Rollup, esbuild, terser, and other modern bundlers.
Multi-map resolution: upload multiple source maps and the tool intelligently matches frames to the correct map by file name, basename, or .map extension.
Original position lookup: resolves minified file names, line numbers, and column numbers back to original source coordinates.
Function name restoration: shows original function names when available in the source map.
Source context display: extracts surrounding source lines (±3) from sourcesContent in the source map for debugging context.
Error signature grouping: generates a copyable error signature like 'TypeError@src/utils/api.ts:42' for quick sharing.
Unmatched frame detection: identifies frames where no source map matched so you know what maps to add.
Frame statistics: shows total frames, resolved count, and unmatched count at a glance.
Flexible input: supports drag-and-drop file upload, file picker, or pasting source map JSON directly.
Privacy-first: all source map processing runs entirely in your browser — your source maps never leave your machine.
Stack trace reuse: works alongside the Stack Trace Analyzer — parse first, then resolve with source maps.

Frequently Asked Questions

What bundlers generate source maps?: Source maps are generated by webpack, Vite, Rollup, esbuild, Parcel, and other modern build tools. Make sure sourceMap: true is configured in your production build. Most bundlers generate Source Map v3 format.
Why are some frames still showing as unmatched?: Unmatched frames occur when no matching source map was uploaded. Production bundles often have separate source maps for app code and vendor/dependency code. Upload all relevant .map files from your build output.
Can I use this without uploading source maps?: No — source maps are required to resolve minified code back to original source. Without a source map, you'll only see the minified file names, lines, and columns that already exist in the stack trace.
Why don't I see the original function name?: Function names may be mangled if your bundler enabled terser mangling without preserving names. Try enabling 'mangleProperties' or similar options in your build config to preserve function name mappings.
Is this safe for production source maps?: Yes. All processing happens locally in your browser. The source maps are never uploaded to any server. For additional security, you can run this tool offline after loading it once.
Can I resolve stack traces from error monitoring services?: Yes. Paste any minified stack trace from Sentry, Datadog, New Relic, or similar services. Just remove any proprietary formatting and keep the standard frame lines.
What's the difference between this and the Stack Trace Analyzer?: The Stack Trace Analyzer parses and classifies stack traces but doesn't resolve minified frames. The Source Map Explorer takes stack traces a step further by mapping minified coordinates back to original source files using source maps.

Source Map Explorer — Resolve Minified Stack Traces to Original Source

How to Source Map Explorer Online

Source Map Explorer Features

Frequently Asked Questions

Related Developer Tools

Source Map Explorer — Resolve Minified Stack Traces to Original Source

How to Source Map Explorer Online

Source Map Explorer Features

Frequently Asked Questions

Related Developer Tools