Ship & Quality · LOCAL TOOL

Asset Budget Planner

Choose files in your browser or paste a simple inventory to calculate total bytes, per-file size, and grouped size by extension.

Runs in this page
No API call

WORKSPACEINPUT → RESULT

Your input

LOCAL

Result

Run the tool to see a result.

Your result will appear here. Input is not saved.

Browser-side processingNothing is sent to a tool API.

WHY THIS TOOL EXISTS

A focused job, not a black box.

The report uses file sizes exposed by the browser and keeps selected files in the current page. It helps a team discuss an explicit budget before testing transfer and caching behavior.

How to use it

Choose local files or load the inventory example.
Set a total byte budget.
Review the largest files and extension groups.

TRY A WORKING EXAMPLE

Start with known input.

Load this sample into the workspace, run the tool, and compare the result shown below.

Show sample input

{
  "inventory": "app.js | 48200 | JavaScript\nhero.webp | 93600 | Image\nicons.svg | 8200 | SVG",
  "budget": "150000"
}

Expected sample result from the local tool

3 asset(s) · 150,000 bytes · within budget.

{
  "totalBytes": 150000,
  "budgetBytes": 150000,
  "budgetUsedPercent": 100,
  "largestFirst": [
    {
      "name": "hero.webp",
      "bytes": 93600,
      "type": "Image"
    },
    {
      "name": "app.js",
      "bytes": 48200,
      "type": "JavaScript"
    },
    {
      "name": "icons.svg",
      "bytes": 8200,
      "type": "SVG"
    }
  ],
  "groups": [
    {
      "type": "Image",
      "count": 1,
      "bytes": 93600
    },
    {
      "type": "JavaScript",
      "count": 1,
      "bytes": 48200
    },
    {
      "type": "SVG",
      "count": 1,
      "bytes": 8200
    }
  ]
}

LIMITS AND INTERPRETATION

What the result cannot tell you.

This reports selected file sizes only. It does not calculate compressed transfer size, cache reuse, decoded image memory, or production network timing.

Inputs are processed in this page and are not written to local storage.