[cbravobernal]

The Password field masks input in the editor but stores the value as plain text and outputs it wherever the field's value is output. The docs described it as "a secure input" with "secure handling", listed validation and character limit settings the field doesn't have, and recommended it for API keys, access tokens and credentials.

This PR:

• describes what the field actually does: masked input, value stored as plain text;
• adds a Storage and Output section covering templates and blocks (get_field()), REST when Show in REST API is on, acf_form() inputs, and JSON-LD (excluded);
• removes the validation and character limit claims, since the field only has placeholder, prepend and append settings;
• replaces the credential use cases with advice against storing secrets in the field.

Docs only, no code changes.

Use of AI Tools

Drafted with Claude Code (Claude Opus 5.5), and reviewed and edited by the author.

🤖 Generated with Claude Code

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

Core Committers: Use this line as a base for the props when committing in SVN:

Props cbravobernal.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

---

Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

• @propsbot add <username> to give props to a GitHub user. Requires write access.
• @propsbot remove <username> to leave a user out of the props. Requires write access.
• @propsbot refresh to refresh this list. Adding the props-bot label works too.