Docker Compose YAML Formatter

Docker Compose YAML Formatter

Paste a docker-compose.yml and instantly get a clean, consistently formatted file with services, networks, and volumes ordered the way Docker Compose conventions expect. The formatter validates the file against the modern Compose Spec, flags deprecated keys like the old top-level version field or legacy links, and warns about unknown service options before they cause runtime failures.

Nutzung

1. Fügen Sie Ihre docker-compose.yml into the input area, or click one of the example links to load a sample stack.
2. Pick a key order — Compose convention sorts services in the order Compose users expect (image, restart, environment, ports, volumes, …), Alphabetical sorts strictly A-Z, or Preserve keeps your original order.
3. Choose 2 or 4 space indentation and toggle Compose Spec validation on or off.
4. Read the validation panel for errors, warnings about deprecated keys, and info notices about implicit network references.
5. Copy the result or download it as docker-compose.yml.

Funktionen

• Compose Spec validation – Recognizes top-level services, networks, volumes, configs, secrets, profiles, include, and extension fields (x-*); flags anything else.
• Deprecation warnings – Highlights the legacy top-level version key, links, external_links, and v2-era resource limits that should move under deploy.resources.
• Service-aware key ordering – Reorders each service so identifying keys (image, build, container_name) come first, runtime config (environment, ports, volumes) sits in the middle, and ops concerns (healthcheck, logging, deploy) land at the bottom.
• Reference checks – Detects services that depend on undefined services and warns when a service uses a network that isn’t declared at the top level.
• Service requirements – Verifies every service has at least one of image, build, extends, oder provider, and that restart uses one of the four valid policies.
• Port + healthcheck sanity – Catches malformed port strings, missing target in long-form ports, and healthchecks without a test.
• Three working examples – A Node + Postgres web app, a WordPress + MySQL + Redis stack, and a multi-service build with profiles and resource limits.
• Local + private – All parsing, sorting, and validation runs in your browser. Your Compose file never leaves the page.