Properties Format Guide

About Properties Format

Java Properties files (.properties) are a simple key-value configuration format widely used in the Java ecosystem since Java 1.0 (1996). Each line contains a key-value pair separated by an equals sign (=) or colon (:). Comments start with # or !. The format supports Unicode escapes (\uXXXX), continuation lines with trailing backslash, and special character escaping. Despite its simplicity, Properties remains one of the most commonly used configuration formats in enterprise Java development.

Properties files are central to Java application configuration — from Spring Boot's application.properties and log4j.properties to ResourceBundle internationalization files. The dotted key convention (e.g., app.server.port=8080) provides a lightweight namespace mechanism. While newer formats like YAML and TOML offer richer features, Properties files continue to be preferred for their simplicity, widespread tool support, and guaranteed compatibility across all Java versions and platforms.

Available Conversions

Properties Format Features

• Key-Value Pairs: Simple key=value or key:value syntax per line
• Dotted Keys: Namespace convention (app.server.port) for logical grouping
• Comments: Lines starting with # or ! are treated as comments
• Unicode Support: \uXXXX escape sequences for international characters
• Continuation Lines: Trailing backslash joins the next line
• Escaping: Special characters (\=, \:, \\, \n, \t) can be escaped
• No Data Types: All values are strings — type interpretation is application-specific

Common Uses

• Spring Boot: application.properties for app configuration, profiles, server settings
• Logging: log4j.properties, logback configuration for Java logging frameworks
• Internationalization: ResourceBundle .properties files for i18n message translations
• Build Tools: gradle.properties, Maven settings for build configuration
• Database Config: JDBC connection strings, pool sizes, timeouts
• Application Servers: Tomcat, Jetty, WildFly configuration files
• Testing: Test environment configuration, mock service endpoints