Converter Tools

Properties to JSON Converter

Convert Java .properties files to JSON in your browser. Dotted key nesting, line continuations, Unicode escapes, and JSON to .properties.

.properties input1,025 chars

# Spring Boot application.properties

spring.application.name=order-service
spring.profiles.active=production

# Server
server.port=8080
server.servlet.context-path=/api
server.compression.enabled=true

# Datasource
spring.datasource.url=jdbc:postgresql://db.example.com:5432/orders
spring.datasource.username=app
spring.datasource.password=s3cr3t
spring.datasource.hikari.maximum-pool-size=20

# JPA
spring.jpa.hibernate.ddl-auto=validate
spring.jpa.show-sql=false

# Logging
logging.level.root=INFO
logging.level.org.springframework.web=DEBUG
logging.file.name=/var/log/order-service.log

# i18n entries
welcome.message = Hello, world!
error.required = This field is required.
support.contact : support@example.com

# Multi-line value (line continuation)
description=A short \
  multi-line description that spans \
  several physical lines.

# Unicode escape (Greek alpha)
greek.letter=\u03b1

# Whitespace in key (escaped) and special chars
my\ key=value with spaces and = signs
url.path=https\://example.com/path?q=1&r=2

JSON output

{
  "spring": {
    "application": {
      "name": "order-service"
    },
    "profiles": {
      "active": "production"
    },
    "datasource": {
      "url": "jdbc:postgresql://db.example.com:5432/orders",
      "username": "app",
      "password": "s3cr3t",
      "hikari": {
        "maximum-pool-size": "20"
      }
    },
    "jpa": {
      "hibernate": {
        "ddl-auto": "validate"
      },
      "show-sql": "false"
    }
  },
  "server": {
    "port": "8080",
    "servlet": {
      "context-path": "/api"
    },
    "compression": {
      "enabled": "true"
    }
  },
  "logging": {
    "level": {
      "root": "INFO",
      "org": {
        "springframework": {
          "web": "DEBUG"
        }
      }
    },
    "file": {
      "name": "/var/log/order-service.log"
    }
  },
  "welcome": {
    "message": "Hello, world!"
  },
  "error": {
    "required": "This field is required."
  },
  "support": {
    "contact": "support@example.com"
  },
  "description": "A short multi-line description that spans several physical lines.",
  "greek": {
    "letter": "α"
  },
  "my key": "value with spaces and = signs",
  "url": {
    "path": "https://example.com/path?q=1&r=2"
  }
}

Property entries

Nested keys

Output bytes

1,196

Options

JSON indent

Value typing

Key nesting

Nesting separator

Default is the dot. Use any single character or short string.

Parsed entries

Key	Value	Line
spring.application.name	order-service	3
spring.profiles.active	production	4
server.port	8080	7
server.servlet.context-path	/api	8
server.compression.enabled	true	9
spring.datasource.url	jdbc:postgresql://db.example.com:5432/orders	12
spring.datasource.username	app	13
spring.datasource.password	s3cr3t	14
spring.datasource.hikari.maximum-pool-size	20	15
spring.jpa.hibernate.ddl-auto	validate	18
spring.jpa.show-sql	false	19
logging.level.root	INFO	22
logging.level.org.springframework.web	DEBUG	23
logging.file.name	/var/log/order-service.log	24
welcome.message	Hello, world!	27
error.required	This field is required.	28
support.contact	support@example.com	29
description	A short multi-line description that spans several physical lines.	32
greek.letter	α	37
my key	value with spaces and = signs	40
url.path	https://example.com/path?q=1&r=2	41

Lint warnings

No warnings. Input parsed cleanly.

Spec: the parser followsjava.util.Properties.loadbehavior for separators, comments, escapes, and line continuations.

Privacy: the file you paste, including any embedded passwords or tokens, is parsed locally and never uploaded.

Tips

Spring Boot config to JSON

Use .properties to JSON with Nest by separator and the Auto typing mode. You get the exact same shape Spring uses when it loadsapplication.propertiesagainst@ConfigurationPropertiesclasses.

i18n ResourceBundles

Keep nesting off, leave typing on Strings only, and you get a flat{ "key.path": "translation" }object that i18next, FormatJS, and most front-end translation libraries can ingest directly.

Multi-line values

End a line with a single backslash to continue the value on the next physical line. Leading whitespace on the continuation line is stripped, matching Java behavior.

JSON back to .properties

Switch to JSON to .properties, pick Indexed keys if your app reads arrays aslist[0]-style entries (Spring), or JSON-encoded value when you would rather keep arrays in a single line.

How to use

Pick .properties to JSON or JSON to .properties from the segmented control at the top, or click Swap direction to feed the current output back as the next input.
Paste your .properties file (or JSON object) into the input area. The Load sample button drops in a representative file you can edit. Comments using # or ! are ignored.
For .properties to JSON, choose JSON indent, whether scalar values are auto-typed into numbers and booleans, and whether dotted keys like spring.datasource.url expand into a nested object or stay as flat string keys.
For JSON to .properties, pick the key/value separator (=, :, or space), choose between indexed keys or a JSON-encoded value for arrays, and turn on Escape non-ASCII for legacy ISO 8859-1 ResourceBundles.
Read the result on the right, watch the entry, nesting, and byte counts update, then use Copy output to grab the converted file. Warnings flag duplicate keys, bad Unicode escapes, and key/object collisions with the original line number.

About this tool

Properties to JSON Converter parses Java .properties files and emits a JSON object you can drop into a modern toolchain, a config service that does not speak Java, or a front-end translation library that needs a flat key/value bundle. Paste any .properties file (a Spring Boot application.properties, a log4j or log4j2 config, a Kafka producer or consumer config, a Hibernate persistence config, a Gradle gradle.properties, a Tomcat server.properties, a localization ResourceBundle, or any custom application file) and the tool produces a structured document where dotted keys like spring.datasource.hikari.maximum-pool-size nest one level per dot. The parser implements the rules in java.util.Properties.load: lines starting with # or ! are comments, the key terminates at the first unescaped =, :, or whitespace, surrounding whitespace around the separator is trimmed, blank lines are ignored, and a trailing backslash on a line continues the value on the next physical line with leading whitespace stripped. Backslash escapes inside keys and values cover the full Java spec: \t, \n, \r, \f, \\, \=, \:, \#, \!, \ (escaped space), and \uXXXX Unicode escapes. Duplicate keys behave like the JVM (last value wins) and earlier values are surfaced as lint warnings with the original line numbers so you can see what got overridden. Nesting is configurable: keep the dot as the separator (the default for Spring), pick a different character, or turn nesting off entirely to get a flat object whose keys still contain literal dots (the shape i18next, FormatJS, and most front-end translation libraries expect). Value typing is configurable too: leave everything as strings (safe for round-tripping) or auto-type numbers, booleans, and null. The reverse direction takes a JSON object whose values are primitives, arrays, or nested objects and writes a clean .properties file with your choice of key/value separator (=, :, or space), array handling (indexed keys list.0, list.1 for Spring-style binding, or a single JSON-encoded line), Unicode-escape encoding for non-ASCII characters (legacy ISO 8859-1 ResourceBundles), and an optional header comment. Useful for migrating legacy Java apps to a JSON-based config, exporting translation bundles to front-end teams, diffing two configs by viewing them as JSON, sanity-checking application.properties before a release, and turning a sample .properties snippet in documentation into a JSON object for an SDK. Everything runs locally in your browser, so the configurations you paste here, including any embedded passwords, JDBC connection strings, or signing keys, never leave your device.

Free to use. Works in your browser. No signup, no login.

Related tools

Properties to JSON Converter

How to use

About this tool

You may also like

INI to JSON Converter

Env to JSON Converter

YAML to JSON Converter

TOML to JSON Converter

JSON to YAML Converter

JSON to Java Class Converter