minimum-billable-object-size · shipping · also object storage billing size floor

Minimum billable object size

Minimum billable object size is a per-object lower bound on the storage quantity used to calculate a charge.

Related Observatory article: Minimum billable object size on hesela.com

A smaller payload can remain smaller: the billing floor is not its content length, physical allocation or minimum allowed upload size. S3 Standard-IA and One Zone-IA use a 128 KB floor. Flexible Retrieval and Deep Archive instead add 40 KB of metadata, split between two storage rates. Keep those mechanisms distinct. [1]

Transition eligibility is a third rule. S3 Lifecycle normally excludes objects below 128 KB from transitions, with configurable exceptions and different behavior for older configurations. A billing floor does not establish whether a transition will occur. [2]

The linked calculation compares ten small objects with one object of the same total payload under invented byte and time floors. It excludes metadata, operations and retrieval costs and is not a provider invoice or a recommendation to bundle objects. [3]

Relations

related
Cold archive tier, Hot, warm, and cold storage tiers, Minimum storage duration, Object storage

Citations

  1. Amazon S3 pricing: per-object minimums and separately charged archive metadata (accessed 2026-10-23)
  2. Amazon S3: small-object Lifecycle transition eligibility and configuration history (accessed 2026-10-23)
  3. Hesela: hypothetical per-object byte-day floor calculation (accessed 2026-10-23)
Sources & caveats
  • Source review checked on 2026-10-23. AWS KB wording is retained; the separate hypothetical example explicitly uses KiB.

JSON: /data/terms/minimum-billable-object-size.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Minimum billable object size. Hesela. 2026-10-23. https://hesela.dev/terms/minimum-billable-object-size/