JavaScript Bundle and Source Map Recovery
Open a source map or JavaScript bundle to inspect individual sources and recovered modules.
Recover original source from a supplied map
Source maps with embedded source text can recover exact JavaScript, TypeScript, TSX and other original files, including empty files. Indexed maps and inline base64 or percent-encoded maps are supported. A map without embedded or supplied source text cannot recreate the missing originals.
For a bundle with a separate map, upload their containing ZIP, ASAR, APK or other supported archive with its original directory structure, then select the script or map. Only supplied local companions are read; remote URLs are never fetched.
Split bundled JavaScript into modules
Structural splitting covers supported Webpack, Browserify, Metro and esbuild bundles. A static fallback can recover additional Webpack and Browserify modules. Ordinary scripts may produce one readable file. Formatting a file is not recovery of original modules, names, TypeScript or comments.
Recovered modules are for source inspection. The result is not a promise of a runnable application, and uploaded JavaScript is never evaluated. Binary Hermes bytecode and Unity bundles use their own recovery paths.
Browse and download results
Processing runs on our servers. Browse recovered-sources/ for supplied originals and modules/ for recovered modules. The report records original names, chosen paths, hashes, tool outcomes and available input byte ranges. Download each file or the complete result ZIP.
Input processing is limited to 64 MiB per script or map, source files to 16 MiB each, and each bundle tool to 60 seconds within the shared job deadline. Output also shares the job's byte and file limits. Available partial files survive unsupported input and processing limits; see DECOMPILATION-NOTES.txt and javascript-recovery.json.