Two-way YAML ↔ Properties converter with advanced key extraction. Get keys in Mule-ready formats, filter results, and export with one click.
![ will automatically get the
secure:: prefix when using Keys Only mode.
Two converters in one. Whether you're flattening YAML into properties or rebuilding YAML from flat keys, here's how each direction works.
Use the YAML to Properties tab to flatten a config YAML. Switch to Properties to YAML to reconstruct a nested YAML from flat key=value pairs.
Both tabs support pasting content directly or uploading a file from disk. Works with
.yaml, .yml, and .properties files. No size limit, no
backend.
Going YAML to Properties? Check Keys Only to strip values, then pick ${key} or Mule::p("key") wrapping. Use the filter bar for large configs.
Grab the output via Copy, or download as a .properties / .yaml file for
your Mule project. No reformatting needed.
config.yaml) and flat properties
(config.properties) files for externalizing runtime configuration. YAML is
hierarchical and easier to read; Properties files are flat key=value pairs. Mule 4 on CloudHub
often uses Properties files for environment-specific overrides.database.host) without the values. This is useful when you need a list of
property keys to reference in DataWeave expressions or to create a Mule property placeholder
template.Mule::p("key") is a DataWeave function that reads a Mule
property at runtime. It's the recommended way to reference properties inside DataWeave scripts,
replacing the older ${key} placeholder syntax in certain contexts. This tool can
auto-wrap all your keys in this format with a single click.![ are recognized as Mule Secure Property
encrypted values. In Keys Only mode, these keys automatically get the secure::
prefix added (e.g., secure::database.password), which is required by the Mule
Secure Properties Module..properties file, and the tool will reconstruct the nested YAML hierarchy
from the dotted key paths, so database.host=localhost becomes proper nested YAML
structure.Practical articles on MuleSoft configuration, DataWeave, and secure deployments.