Skip to main content

How to reduce the size of Stylus WASM binaries


Stylus is currently tagged as an alpha release. The code has not been audited, and should not be used in production scenarios. This documentation is currently in public preview.

To provide feedback, click the Request an update button at the top of this document, join the Arbitrum Discord, or reach out to our team directly by completing this form.

To be deployed onchain, the size of your uncompressed WebAssembly (WASM) file must not exceed 128Kb, while the compressed binary must not exceed 24KB. Stylus conforms with the same contract size limit as the EVM to remain fully interoperable with all smart contracts on Arbitrum chains.

The Stylus CLI automatically compresses your WASM programs, but there are additional steps that you can take to further reduce the size of your binaries. Your options fall into two categories: Rust compiler flags, and third-party optimization tools.

Rust compiler flags

The Rust compiler supports various config options for shrinking binary sizes.


codegen-units = 1 # prefer efficiency to compile time
panic = "abort" # use simple panics
opt-level = "z" # optimize for size ("s" may also work)
strip = true # remove debug info
lto = true # link time optimization
debug = false # no debug data
rpath = false # no run-time search path
debug-assertions = false # prune debug assertions
incremental = false # no incremental builds


target = "wasm32-unknown-unknown"

rustflags = [
"-C", "link-arg=-zstack-size=8192", # shrink the heap

nightly flags

Additional unstable nightly flags may help too.

cargo +nightly build -Z build-std=std,panic_abort -Z build-std-features=panic_immediate_abort

The above configures the standard library to not include panic strings, which are useless on chain but may take up considerable space.

cargo stylus deploy --nightly

Third-party optimization tooling

Additional WASM-specific tooling exists to shrink binaries. Due to being 3rd party, users should use these at their own risk.


wasm-opt applies techniques to further reduce binary size, usually netting around 10%.

Frequently asked questions

Will future releases of Stylus introduce additional optimizations?

Yes! We're actively working on improving WASM sizes generated by Rust code with the Stylus SDK.

Why don't I have to worry about this type of optimization when I use cargo without using Stylus?

On modern platforms, tools like cargo don’t have to worry about the size of the binaries they produce. This is because there’s many orders of magnitude more storage available than even the largest of binaries, and for most applications it’s media like images and videos that constitutes the majority of the footprint.

Resource constraints when building on blockchains are extremely strict. Hence, while not the default option, tooling often provides mechanisms for reducing binary bloat, such as the options outlined in this document.