Developer
Bundle Size Calculator
Estimate bundle totals, asset mix, and rough text gzip cost from a pasted build output or simple file-size list.
Asset listPaste build output rows
4 files
javascript • 235.4 KB
javascript • 82.0 KB
stylesheet • 21.5 KB
image • 5.9 KB
Accepted input
Use one asset per line. Both "file.js 12kb" and "file.js, 12kb" formats are supported.
Use this tool when
These are the practical situations where this workflow usually earns its keep.
You need to estimate the impact of assets and dependencies on shipped size.
You want a browser-local pass before prioritizing which parts of the bundle deserve optimization next.
You need a smaller, cleaner review surface during frontend performance review.
Daily workflow acceleration
Bundle Size Calculator helps when teams need to estimate the impact of assets and dependencies on shipped size without opening a heavier system or rebuilding the same transformation manually every time.
Review and handoff clarity
A focused output is useful when the next step is prioritizing which parts of the bundle deserve optimization next and the current raw input would otherwise slow down the reviewer or teammate.
Lower-friction local handling
For frontend performance review, keeping the task in the browser is helpful because the source material often does not need to leave the user’s machine just to answer this one question.
Common mistakes to avoid
These are the checks that usually keep the output useful instead of misleading.
Bundle estimates are directional unless you compare them with the real build artifacts and runtime behavior.
Using a summary as a substitute for reading the source artifact when the change is high risk.
Forgetting that generated snippets and reviews may need project-specific edits before use.
Learn how to use this tool
Estimate asset totals, file mix, and rough gzip impact from pasted build output. This guide focuses on how teams use it for frontend performance review when the real job is to estimate the impact of assets and dependencies on shipped size.
Read the guideTell us what is missing
If this flow helped only partly, leave feedback so we can understand the missing step or edge case.
Leave feedbackRequest the next tool
Use the wishlist to suggest the next utility, workflow, or improvement that would complete this job to be done.
Open wishlistRelated tools
These tools often appear right before or right after this workflow.
Docker Optimizer
Review Dockerfiles for repeatability, image size, and runtime hygiene inside the browser.
Open toolGitignore Builder
Generate a starter .gitignore locally from common stack sections like node, python, dotnet, and logs.
Open toolFixture File Generator
Generate local image, audio, video, PDF, CSV, and Excel fixtures for upload QA and boundary testing.
Open tool