To manage gas costs effectively on Sui, you need to focus on minimizing the number of mutated objects and being selective with what you include in batched transactions. Each object you read or mutate increases gas usage, especially shared or dynamic fields. When batching actions, avoid including unnecessary reads or complex logic that could trigger expensive computation. You can estimate gas usage using the sui client dry-run command before sending a transaction, which helps avoid surprises. Also, design your Move modules with gas in mind — reduce calls to external modules, avoid excessive storage writes, and use immutable reads where possible.

If you're creating a frontend app, try grouping user actions smartly — for instance, only batch transactions if it benefits the user in one click rather than doing multiple operations that could be separated. Finally, keep an eye on network congestion. Sui’s gas pricing can vary depending on load, so time your interactions or build in fallback strategies.

🔗 Learn more about gas estimation on Sui

To save gas on Sui, the key is keeping things light. Every object you read or change (especially shared ones or dynamic fields) adds to the gas cost. So try to mutate fewer objects and only batch stuff if it truly helps the user