ICPay Blog

Technology

ICP Cycles Explained

Gas is the fee every blockchain user knows. The Internet Computer runs on something different: cycles, a unit of computation that is stable, predictable, and paid by the developer rather than the user. Here is what cycles are, what they cost, and how the economics work.

August 16, 2026 · 6 min read

What cycles are

A cycle is the Internet Computer's unit of metered computation. Canisters consume cycles for every resource they use — CPU instructions, storage, and network operations. Think of cycles as the fuel gauge of a canister: it burns a little on every update call and every byte it stores.

Where a traditional cloud bills in US dollars per CPU-hour and a blockchain bills in gas denominated in its own volatile token, ICP bills in cycles. That choice matters because of how cycles are priced.

The XDR peg

Cycles are pegged to the Special Drawing Right (XDR) — a basket of major currencies maintained by the IMF. The rule is simple:

1 trillion cycles = 1 XDR (roughly $1.30–$1.40 USD).

This peg is deliberate. ICP's token price fluctuates with markets, but the cost of running a canister should not swing with the price of ICP. A developer who buys cycles at one price can predict what a month of hosting will cost regardless of what the token does.

What running a canister costs

Costs are published by DFINITY and metered per operation. The numbers give a feel for the scale:

  • 1 GB of storage for a year — roughly 127 trillion cycles, about $175–$190 per year at the XDR peg (subnet-dependent; some sources quote ~$5/GB/year on storage-only terms — always check the current cost reference).
  • 1 million compute instructions — about 4,000 cycles, a fraction of a cent.
  • An HTTPS outcall — about 49 million cycles per call.
  • An inter-canister call — about 260,000 cycles.
  • A threshold ECDSA signature — about 22 billion cycles.
  • Creating a canister — about 100 billion cycles.

Queries — read-only calls — are free. They are served from replicated state without consensus and burn no cycles, which is why an app can check a balance on every keystroke without cost.

The reverse gas model

Here is the key difference from most blockchains: users do not pay gas. The canister pays for itself out of a prepaid balance of cycles.

A developer buys ICP, converts it to cycles inside the NNS, and tops up their canisters the way a founder tops up an AWS account. From the user's perspective, interacting with an ICP app is indistinguishable from a normal website — no gas token, no approval popups, no wallet installs.

ICP, cycles, and deflation

Converting ICP into cycles burns the ICP. Every conversion removes tokens from supply. When network usage is high, that burn creates deflationary pressure — the opposite of a gas token, which tends to be spent and recycled rather than destroyed.

Cycles, by contrast, never inflate. They are tied to XDR, so their purchasing power is stable by construction. That combination — burning ICP to mint a stable-priced fuel — is one of the most distinctive parts of the token's design.

Why cycles matter for businesses

For products like ICPay Cloud, the economics are what make on-chain storage practical. Billing in ICP for a 30-day bucket plan is really a way of pre-paying the canister's cycles. The developer knows the cycle cost of a gigabyte-month, adds a margin, and charges users a predictable flat price — while the underlying infrastructure cost stays stable because cycles are XDR-pegged.

Useful links

Related reading