CDN & Storage Cost Calculator

Every storage and CDN evaluation stalls on the same question: what will this actually cost me each month? This CDN storage cost calculator answers it before you sign up or hand over a card. You enter four things — how much you store, how much you serve to users each month, your average file size, and roughly how many requests you handle — pick whether files go out through a CDN or straight from the bucket, and you get a monthly cdn22.net estimate broken into storage, delivery, and request fees.

The estimate is deterministic (the same inputs always produce the same number), runs entirely in your browser, and needs no login.

The reason a file storage pricing calculator is worth running at all is egress. Storage is the cheap, predictable half of the bill; bytes leaving to your users is the half that moves. On a build-it-yourself stack, egress fees are a separate metered line — S3 transfer out to the internet, or CloudFront data transfer out, plus per-request charges on both services — so the same library costs wildly different amounts depending on how often it gets downloaded.

That is what an S3 egress cost calculator is really measuring, and it is why the calculator shows you your egress-to-library ratio: serve your whole library twice a month and storage dominates; serve it fifty times and delivery is the entire bill.

So the estimate shows two columns. The first is your cdn22.net cost: one per-GB rate for storage, one for delivery, and $0 in request fees, drawn from prepaid credits with no separate egress invoice, no monthly minimum, and no per-seat pricing. The second is the same bytes priced at the AWS list-price baseline this site's own pricing model is built on — S3 Standard storage plus either CloudFront or S3 internet egress, at first-tier us-east-1 / North America list rates — shown so the CDN bandwidth cost comparison is explicit rather than implied.

Be aware of what that reference column leaves out: per-request fees, cross-service data transfer, cache invalidations, and the IAM policies, bucket configuration, and distribution you would set up and keep running. cdn22.net's blended per-GB rate is higher than raw AWS list price precisely because it bundles CDN delivery, requests, and that operational surface into one number.

The honest framing is bundled-and-predictable against a stack you assemble and operate yourself — not a cheaper-per-gigabyte claim.

When you are done sizing the budget, the product behind the number is plain REST: upload a file through the API (POST /v1/files/{folderId} for a presigned URL and id → PUT the bytes → POST /v1/files/confirm-upload), mark the folder public for a permanent CDN link, or keep it private and mint expiring signed URLs. If you want the fuller comparison rather than just the arithmetic, read the S3 alternative breakdown and how the no-egress-fee storage model works, then start with prepaid credits and confirm the real numbers against your first month of usage.