Source Map Inspector

Look up positions in a flat version-3 source map and report source inventory without exporting embedded source text.

Inputs stay on your device No sign-up Free to use
How this works

The tool runs in this browser. Your file or text is not uploaded to UseFreeTools. Check this tool's limits for anything it may save on your device.

Privacy details

Inspect source map controls

Flat version-3 maps only, up to 2 MiB, 1,000 sources and 100,000 segments. No code is executed.

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

Showing a generated example. Generate again for a new result.

How to use Source Map Inspector

  1. Paste a bounded flat version-3 map with sources, names and mappings.
  2. Enter a one-based generated line and zero-based column.
  3. Review the preceding mapping segment and source exposure inventory, then export the report.

Example: Source Map Inspector

Look up positions in a flat version-3 source map and report source inventory without exporting embedded source text.

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

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.

Supported inputs and limits

Flat version-3 maps up to 2 MiB, 1,000 sources, 10,000 names, 100,000 generated lines and 100,000 segments. Indexed sections and remote sources are unsupported; malformed VLQ and out-of-range offsets are refused.

Where your input is processed

This tool processes your input in this browser. Your text and files are not uploaded to UseFreeTools. Check this tool's limits for anything it may save 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.

Project manager: Tony Hines · Content updated 4 October 2026 · Report a problem