# Inconsistent rendering of vaulted inline vs. file vaulted variables
If vaulted inline variables render differently than vaulted file variables, normalize the decrypted data through JSON and back: `data | to_json(vault_to_text=True) | from_json | to_nice_yaml`. That strips the inconsistent vault formatting. The maintainers say they are still looking for a permanent fix.
## Context from the issue
gh:ansible/ansible#85722: Issue ansible/ansible#85722 (closed, 15 comments): ### Summary When a variable is defined inline using the `!vault` tag, rendering behavior differs depending on context since 2.19. Direct references resolve to the decrypted value, but the same variable remains encrypted when rendered via `to_nice_yaml`. If the entire file is vaulted with `ansible-vault encrypt`, this problem does **not** occur. This makes variable substitution unpredictable and requires workarounds. ### Issue Type Bug Report ### Component Name vault ### Ansible Version ```console ansible [core 2.19.0] config file = [HOME]/... configured module search pat