Menu

YAML Obfuscator - Reversible Key & Value Obfuscation

Real parser. Real obfuscation. Rename keys and encode string values with a downloadable mapping file that restores the original exactly.

YAML Obfuscation Studio Reversible
Ready
YAML Source 0 lines • 0 chars
Obfuscated Output 0 lines • 0 chars
Safe mode. Comments and blank lines are removed. All keys and values are preserved. Enable "🔒 Obfuscate Values" or "🔑 Rename Keys" above to actually obfuscate.
Complete Guide to YAML Obfuscation

How This Tool Works

This obfuscator parses the YAML into a structured tree first, then applies transformations on the tree. This guarantees it never corrupts values like "80:80", URLs, or passwords. Numbers, booleans, nulls, and multi-line strings are never touched.

Modes

ModeWhat ChangesReversible?
Safe (default)Comments and blank lines removedN/A
🔒 Obfuscate ValuesString scalars Base64-encodedYes (mapping file)
🔑 Rename KeysKeys renamed to random identifiersYes (mapping file)

Example — Simple YAML

Input:

name: Ahmed

Obfuscated (🔒 ON):

name: "QWhtZWQ="

Mapping:

[Values]
# format: <encoded> => <original>
QWhtZWQ= => "Ahmed"

Decoded:

name: Ahmed

What Gets Preserved

YAML TypePreserved?
Numbers (5432, 1.5)✅ Never encoded
Booleans (true, false)✅ Never encoded
Nulls (null, ~)✅ Never encoded
Multi-line strings (|, >)✅ Never encoded
Anchors/aliases (&a, *a)✅ Never encoded
Document separators (---)✅ Preserved
String scalarsEncoded when option ON (reversible)
KeysRenamed when option ON (reversible)

Warning — Docker and Kubernetes

When 🔒 Obfuscate Values or 🔑 Rename Keys is enabled, the resulting YAML is not directly executable by Docker Compose, Kubernetes, or CI/CD tools. Those tools expect the original keys and raw values. You must reverse the obfuscation with the mapping file before using the YAML.

Frequently Asked Questions

Is Base64 encryption?
No. Base64 is a reversible encoding, not encryption. Anyone with the obfuscated value and a Base64 decoder can reverse it in seconds. This tool uses it for structural preservation, not security.
Does the decode test prove correctness?
Yes. After obfuscation, the tool re-parses the output and applies the mapping in reverse. If the restored YAML's structure matches the original, the "Decode round-trip PASSED" message appears. If not, it fails visibly.
Why are numbers and booleans not encoded?
YAML is type-sensitive. Encoding 5432 to a string makes Docker see a string instead of a port number. Encoding true turns a boolean into a string. Both break consumers. Only string scalars are encoded.
Does it work with ports like "80:80"?
Yes. "80:80" is a quoted string scalar. When encoding is enabled, it becomes a Base64-encoded quoted string, and the mapping lets you decode it back to "80:80" exactly.
Is my YAML uploaded to your server?
No. All processing happens in your browser using JavaScript. Your YAML never leaves your device.
Can I use this for commercial projects?
Yes. Obfuscate any YAML you own or have rights to modify.

Related Tools