FixesUpdated 23 Oct 20261 min read

"Computational budget exceeded" on Solana: fix

The fix

The transaction ran out of compute units. Each instruction gets 200,000 by default and a transaction can use at most 1,400,000.

What the error means

Computational budget exceeded

The transaction ran out of compute units. Each instruction gets 200,000 by default and a transaction can use at most 1,400,000.

Where it comes fromSolana runtime (instruction error)
CodeComputationalBudgetExceeded

How to fix it

  1. Raise the compute unit limit with a SetComputeUnitLimit instruction, up to 1,400,000 per transaction. Many wallets and bots do this for you with a "compute" or "CU" setting.
  2. Split a large action into several transactions, for example fewer recipients per airdrop transaction or fewer bins per liquidity add.
  3. If you set the limit yourself, simulate first and use the units consumed plus a margin.

If that is not it

  • If the limit is already at 1,400,000, the transaction does too much work for one transaction and must be split.

More fixes: how to decode any Solana error code and why Solana transactions fail.

Source

Error text and code from Solana SDK transaction and instruction error definitions (anza-xyz/solana-sdk); Solana fee documentation, read on 24 October 2026.

Questions people ask

How many compute units can a Solana transaction use?

Up to 1,400,000. The default is 200,000 per instruction.

Does raising the limit cost more?

Only if you also set a compute unit price; the priority fee is price times limit.

"Computational budget exceeded" on Solana: fix | Jumpbit