Google Style Guides

What they are

Google publishes copies of its internal style guides so that people contributing to Google-originated open source projects know the conventions to follow. The site lists guides for C++, C#, Go, HTML and CSS, Java, JavaScript, JSON, Markdown, Objective-C, Python, R, Shell, Swift, TypeScript, Common Lisp and Vim script, and links out to guides for Angular, Dart and Kotlin.

Google is explicit that the guides apply to its own projects. Every major open source project has its own style guide, and nobody requires you to follow Google's. They are included here because they are clear, detailed and explain their reasoning, which makes them an excellent default when you do not have one.

Why a style guide matters for clean code

Consistent naming and formatting remove a whole category of distraction. When every file looks the same, reviewers can focus on design and correctness instead of arguing about braces and spacing. A good guide also carries real design advice: how to name things, how long functions should be, how to handle exceptions and when to comment.

What to read for each language

• Java: the Java Style Guide covers source file structure, formatting, naming and programming practices such as handling caught exceptions.
• Python: the Python Style Guide covers language rules, such as exceptions, imports and default arguments, and style rules, such as naming, docstrings and line length. It builds on PEP 8, Python's official style guide.
• TypeScript: the TypeScript Style Guide covers source file structure, language features, naming, the type system and comments.
• C#: the C# Style Guide covers naming and formatting conventions for C# code.

Read the naming and comments sections first; they give the most value for the least time.

How to use them

Do not memorise a style guide. Read it once to understand the reasoning, then let a formatter and linter enforce the mechanical parts automatically. Keep the guide open as a reference for the judgement calls a tool cannot make, such as naming and when to comment.

Common questions

Should my team adopt Google's guide? If you have no guide, it is a reasonable starting point. If your language community has a standard, such as PEP 8 for Python or Microsoft's C# conventions, many teams follow that instead.

Can I reuse the text? The guides are published under the CC-By 3.0 licence.

Best for: learners who want concrete, well-reasoned conventions for naming, formatting and structure in their language.