JavaScript Bundle & Source Map Analyzer

Private build forensics

Inspect bundle composition, Source Maps, budgets and build deltas without executing imported code.

Imported bytes

1.30 MiB

Measured Gzip

220 B

Assets

Modules

Chunks

Findings

Build assets

Actual files override metadata-only sizes when names match.

webpack · sourcemap

Asset or module	Kind	Size	Gzip	Chunk
assets/vendor.a81e30cd.js	javascript	793.0 KiB	—	vendor
assets/app.3f21ac9e.js	javascript	474.6 KiB	—	app
assets/app.82d3fa91.css	css	62.5 KiB	—	app
assets/app.3f21ac9e.js.map	map	282 B	220 B	—

Total build bytesPass

1.30 MiB / 2.00 MiB

Largest entryFail

793.0 KiB / 500.0 KiB

Largest assetFail

793.0 KiB / 750.0 KiB

Largest moduleFail

277.3 KiB / 200.0 KiB

Fail when Source Maps embed source textPass

true / false

01
Open build evidence
Import bounded stats, metafiles, manifests, maps and actual assets without executing code.
02
Trace size and mappings
Explore assets, modules, chunks, compressed bytes, VLQ mappings and privacy findings.
03
Compare and enforce
Load a baseline, apply explicit budgets and export a source-free review report.

Is imported JavaScript executed?

No. Files are treated as text or structured metadata and are never evaluated.

Which build tools are supported?

Webpack stats, esbuild metafiles, Vite or Rollup manifests, Source Maps and actual JS or CSS files are recognized.

Are compressed sizes exact?

Gzip is measured for actual imported assets; metadata-only reports cannot reconstruct compressed module bytes.

Can this prove tree shaking or runtime performance?

No. Static build evidence must be combined with runtime profiling and production measurements.

Keep working with other focused browser utilities.