Source Map Inspector

Find an original source position from a supplied source map and generated location.

On-device No sign-up Free to use

Inspect source map controls

?

Flat version-3 JSON up to 2,097,152 characters, 1,000 sources and 100,000 segments. No code is executed.

Processed in your browser. Your inputs stay on this device.

Showing an example. Change the fields, then use inspect source map to update it.

Result

Showing an example.

Map generated line 2, column 0 to src/main.js line 2, column 0 in the supplied tiny map.

Original position: src/main.js, line 2, column 0. Mapping starts at generated line 2, column 0.

Loading the tool. Your result will appear here.

https://usefreetools.net/source-map-inspector · 20 November 2026

Was this helpful?

How to use Source Map Inspector

  1. Paste a supported flat version-3 source-map JSON value. Indexed sections are refused; no generated or original code is run.
  2. Enter the generated line starting at 1 and column starting at 0. Read the updated nearest preceding segment on that same line.
  3. Review unmapped gaps and source names/embedded-content counts. The inspector does not fetch sourceRoot or show sourcesContent text.
  4. Download the report if useful and inspect paths before sharing. It omits embedded code but does not prove a deployed map is private or complete.

Example: Source Map Inspector

Map generated line 2, column 0 to src/main.js line 2, column 0 in the supplied tiny map.

You add
Version 3 source map (JSON): { "version": 3, "file": "app.js", "sources": [ "src/main.js" ], "names": [ "greet" ], "sourcesContent": [ "function greet() {}" ], "mappings": "AAAAA;AACA" }; Generated line (starts at 1): 2; Generated column (starts at 0): 0
You get
Original position: src/main.js, line 2, column 0. Mapping starts at generated line 2, column 0.

Options

Position convention
Generated and original lines are displayed from one; columns start at zero. Lookup stays on the requested generated line.
Embedded source
The report counts sourcesContent characters but omits the actual embedded code from downloads. Source paths themselves can be sensitive.
Version 3 source map (JSON)
Flat version-3 JSON up to 2,097,152 characters, 1,000 sources and 100,000 segments. No code is executed.

Supported inputs and limits

  • Pasted flat version-3 JSON up to 2,097,152 characters;
  • 1,000 sources, 10,000 names, 100,000 generated lines and 100,000 segments.
  • Indexed sections, malformed VLQ and out-of-range offsets are refused.
  • Lookup never borrows a mapping from another generated line; a one-field segment ends mapping for its region.
  • Reports omit embedded source text but retain source paths, sourceRoot and counts.
More details

No external source fetch, code execution or live exposure check.

Where your input is processed

This tool does not upload your inputs. See the limits for anything saved on your device.

A mapping does not cover every nearby character

Lookup uses the greatest preceding segment on the same generated line. A one-field segment marks an unmapped region rather than carrying a previous source mapping forward. The tool does not execute code, fetch sourceRoot addresses or establish whether a deployed server exposes the map.

Questions about Source Map Inspector

Can I inspect indexed sections?

This version accepts flat maps only and refuses indexed maps.

Is embedded code copied into the report?

Only its presence and character count are exported.

Why can lookup be unmapped?

The preceding segment can explicitly stop a mapping, or the line may have no applicable segment.

Page updated · Project managed by Tony Hines · Report a problem with Source Map Inspector