Check the size impact of npm package imports with minified and gzipped size estimates.
Paste JavaScript import statements to inspect the estimated code weight associated with their npm packages. The tool reports separate minified and gzipped figures, helping distinguish compact bundle size from compressed transfer size. It is intended for quick dependency comparisons, not exact production measurements. The most common mistake is treating the gzipped estimate as the package's installed size or as a guarantee of what users will download. A finished bundle can differ because its package versions, retained exports, shared dependencies, and chunk boundaries are build-specific.
The input consists of JavaScript import declarations referring to npm packages. For each recognized package specifier, the estimator presents minified and gzipped size estimates. A package-root specifier and an exposed package subpath can represent different entry points, so compare results only for the exact import forms you intend to use. The pasted declarations are processed in the browser and are not uploaded.
The minified figure estimates a compact representation of the imported JavaScript. The gzipped figure estimates its compressed representation and is the more relevant number when comparing gzip transfer weight. Their difference comes from compression, not additional feature removal. Both remain estimates because a complete build may discard exports, combine modules, split chunks, or share dependencies among several imports.
No. It is an estimate associated with the import, not an observation from your production deployment. The final download can change with the selected package version, bundler transformations, tree shaking, shared modules, source maps, chunk boundaries, and server compression. Build the application in production mode and inspect its emitted assets when exact transfer bytes matter.
Not by itself. It can show the estimates available for import forms it recognizes, but it cannot establish exactly what your bundler will retain. Verify the result with a production bundle report, especially when the package mixes module formats, declares side effects, re-exports other modules, or contributes dependencies already present elsewhere in the application.
The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Format, validate, and beautify JSON with syntax highlighting and error detection.
Encode text or files to Base64 and decode Base64 strings back to their original form.
Format and indent SQL queries for better readability across all major dialects.
Convert HTML markup into clean Markdown syntax with support for tables and lists.
Write Markdown and see the rendered HTML output in real time with live preview.
Visualize unified diffs and patch files with color-coded additions and deletions.