Neatbo.

Recover embedded Source Map sources

Recover actual sourcesContent text from a local v3 source map or an explicit inline data URI, with a complete availability index.

Browser-local processingInputSource Map / inline source fileOutputRecovered-source ZIP / availability indexUp to 5 MiB per file · File limit: 1
  1. 1Add input
  2. 2Review and run
  3. 3Get your result

Tool input and files are processed in this browser without being uploaded.

Your input

Inputs are kept temporarily in this tab when switching tools. Refreshing or closing clears them; large results may need to be regenerated.

⌘ / Ctrl + Enter to run

or drag and drop it here

Files stay on this device. Your originals stay unchanged.

.map · .json · .js · .css

Up to 5 MiB per file · File limit: 1

    0 characters · 0 bytes
    Preparing the tool…

    Before you start

    Restore source files that were embedded in a build's source map. Every source index stays distinct, including duplicate names and empty files. Null or missing sourcesContent is reported as unavailable; mappings are never used to invent source code.

    How to use this tool

    1. Paste a v3 map or choose a local map/JS/CSS file.
    2. Recover and inspect which sources are present, null or unavailable.
    3. Download the available-source ZIP and full mapping reports.

    Supported inputs and limits

    One input up to 5 MiB, pasted text up to 1 MiB, 2,000 source records and 30 MiB recovered UTF-8 text. Reports are bounded to 20 MiB each.

    Ordinary source-map v3 with sources, names and mappings; indexed sections are unsupported. JS/CSS input must end with one explicit inline application/json sourceMappingURL data URI. No code execution or remote requests. Recovered text is encoded as UTF-8, without claiming the original file's wire encoding. Safe ZIP names include source indices; source URLs have credentials/query/fragment removed from reports.

    Worked example

    Example input

    A v3 map contains Unicode text, an empty file, null content and a second duplicate path.
    Example options
    {}

    Example output

    3 actual text files recovered; 1 unavailable source reported; duplicate indices remain separate.

    When something does not work

    Provide an ordinary v3 map with valid paired arrays or a single final inline data URI. Fix duplicate JSON keys, malformed encodings or excessive payload; rerun with supported input.

    Frequently asked questions

    Can it reconstruct sources that were not embedded?

    No. Absent or null sourcesContent is explicitly unavailable and no remote source is fetched.

    Are duplicate source paths overwritten?

    No. Every source index gets its own safe output path and appears in the mapping report.

    Documentation & further reading

    Recorded file guide: subtitles, EML, HAR and byte comparisons →Read what a captured file actually contains →

    Related tools