Google Java Style Guide: Comprehensive Coding Standards and Best Practices

The document defines the full Google Java programming style, stating that a source file must be named after its top‑level class with a .java extension and encoded in UTF‑8.

Only ASCII space (0x20) is allowed as whitespace; tabs are prohibited, and line length should respect an 80‑ or 100‑character column limit with automatic wrapping when necessary.

Braces follow the K&R (Egyptian) style: opening braces stay on the same line as the statement, and closing braces are placed on a new line, with a minimum of two spaces indentation for each new block.

Import statements must be explicit (no wildcards), placed on separate lines, and grouped in the order: static imports, com.google imports, third‑party imports, java imports, then javax imports, each group separated by a blank line.

Class declarations are limited to a single top‑level class per file; members should be ordered logically, and overloaded methods or constructors must appear together without intervening code.

Naming conventions enforce UpperCamelCase for classes, lowerCamelCase for methods, parameters, and local variables, CONSTANT_CASE for static final constants, and lowerCamelCase for non‑constant fields.

Comments may use block /* ... */ or line // ... style, with multi‑line block comments aligning asterisks vertically; Javadoc blocks start with /** , include a brief summary, optional paragraphs, and tags such as @param , @return , @throws , and @deprecated .

Annotations occupy their own line before the element they annotate, and static members should be accessed via the class name rather than an instance.