Why 315.15 MiB and 330.5 MB can describe the same data

A megabyte (MB) is 1,000,000 bytes. A mebibyte (MiB) is 1,048,576 bytes. Kino’s manifest budget is approximately 315.15 MiB, or 330.5 MB. A difference in those labels is not automatically a download bug.

Its decoded map-data estimate is approximately 887.71 MiB. That is a different quantity. The compressed transfer budget excludes the engine, scripts, optional movies, HTTP overhead, retries and some fallback paths.

QuantityMeaningUse
Compressed map budgetSum of manifest transport estimatesPlan approximate data transfer.
Decoded map dataManifest file sizes after decodingUnderstand why storage is larger.
Actual network bytesMeasured browser responses for a specified runEvaluate that run, not every launch.
Browser storage estimateApproximate origin quota and usageSpot obvious constraints, not guarantee allocation.

What a warm launch can reuse

The preserved downloader validates files and can retain them in OPFS for the same website origin and browser profile. A later launch can reuse those files, while still fetching page code or preparing the engine.

Different browsers, private windows, the pages.dev hostname and the primary domain have different storage contexts. Returning after eviction or changing the build can require more data. No offline launch guarantee follows from having cached one map.

Before clearing the cache

  1. Save the exact error and map URL. Clearing first can remove useful evidence and force a large redownload.
  2. Check normal-window storage permissions and available device space.
  3. If you choose to remove data, use browser site-data settings for the exact hostname. Close game tabs first.
  4. Expect cached maps and saved privacy choices on that origin to be removed. Other domains can have their own cookies and need separate deletion.
  5. The next authorized game launch may be cold. Do not compare its time with a warm launch as though the connection got slower.

Per-map budgets and measurement limits

The comparison page reads the preserved ten-map manifest report dated October 10, 2026. These are archive budgets, not a fresh speed test or a promise that resources are currently being served.

Historical tests with an intercepted request path or an existing OPFS cache are useful functional evidence but do not measure normal CDN cold/warm behavior.

Sources and scope