Google developer documentation style guide
The Google developer documentation style guide is a free public style reference for writing technical content for software developers. Google's own technical writers use it across developer-facing documentation.
Also known as:
Google developer style guide, Google style guide
What is Google developer documentation style guide?
The Google developer documentation style guide is the editorial rulebook Google uses for its developer content, available publicly at developers.google.com/style. It specifies voice, tone, grammar, word choice and formatting patterns tuned for API documentation, tutorials and reference material. For example, the guide recommends second person, active voice, present tense and the serial comma, which makes instructions feel direct and unambiguous.
Why does Google developer documentation style guide matter?
Google's guide matters because API and SDK documentation often gets contributions from many authors, and a shared style keeps the reading experience consistent. Teams shipping open source projects, developer portals or integration guides use it as a ready-made baseline, which saves weeks of internal debate. Its clarity-first approach has influenced how most modern developer docs read, including guides for Kubernetes, AMP and Dart.
Examples of Google developer documentation style guide
Voice — Second person, active voice and present tense: "The function returns a string" rather than "A string will be returned by the function."
Serial comma — The guide uses the Oxford comma, so "strings, arrays, and objects" keeps the final comma before "and."
Headings — Sentence case for section headings, so "Get started" rather than "Get Started."
