Google's Rust Style Guide

A closer look at Google's Rust Style Guide

What Google’s Rust Style Guide is

This is a style guide for using the Rust programming language at Google. It covers more than formatting: it includes API design, implementation guidance, code organization, ownership and borrowing, concurrency, documentation, unsafe code, and testing practices. The guide is aimed at bringing consistency across Google codebases that use Rust, including places like Android, ChromeOS, Fuchsia, and Chrome.

What you can actually do on the guide page

Read concrete recommendations and rules such as preferring small crates, naming source files after primary items, importing type names unqualified, using rustfmt for formatting, avoiding Rc and Arc, preferring borrows over deep copies, preferring enum over bool for APIs, and avoiding async/.await in some contexts. The guide explains when API design rules are binding (library code) versus strongly recommended (application code) and gives guidance on module layout, imports, traits, generics, and test framework choices.

Who will find this useful

Rust developers working in Google codebases or on projects that follow Google-originated open-source practices. Reviewers and authors of Rust code who need consistency for readability and large-scale refactors will benefit. It is also relevant to engineers deciding whether a rule is mandatory for library code or advisory for application-specific code.

Questions people ask about Google's Rust Style Guide

Does the guide replace the official Rust style rules?

No; it says to follow the official public Rust style rules except where they conflict with this guide, and it notes most formatting is enforced by rustfmt.

Are API design rules mandatory everywhere?

For library code the API design rules are binding; for application code they are strong recommendations favoring simplicity and directness.

Does the guide cover concurrency and async usage?

Yes; it includes guidance on concurrency, notes handling poison, advises not to use async/.await in some contexts, and recommends not starting new threads through the Rust standard library in certain codebases.

Google's Rust Style Guide was shared on NexURLs by Nexis on October 22, 2026, in Tech & AI.