Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Developer · Guide

How to Use Application Passwords in WordPress

How to Use Application Passwords in WordPress

Short answer

To use an application password in WordPress, open Users and then Profile, scroll to Application Passwords, name the app, and click Add New Application Password. Copy the 24-character password at once, since WordPress shows it only once, then send it with your username as HTTP Basic Auth on REST API calls over HTTPS.

Key takeaways

  • Application passwords arrived in WordPress 5.6 in December 2020 and work only for API calls, not wp-admin logins.
  • Each password is 24 characters of letters and numbers, shown once and stored hashed.
  • One password per app lets you revoke a single tool without changing the main password.
  • Use HTTPS always, since Basic Auth sends the username and password encoded in a header.
  • WP-CLI has managed application passwords since version 2.6.0, with create, list, and delete commands.

What is an application password in WordPress?

An application password is a 24-character password tied to one WordPress user that lets an outside app use the REST API without your main password.

Developer.WordPress.org states that application passwords are revocable, per-application credentials for programmatic access, such as a mobile app, an integration, or a script (checked November 2026).

Application passwords arrived in WordPress 5.6 in December 2020. Make WordPress Core states that WordPress 5.6 introduced this system for making authenticated requests to WordPress APIs (checked November 2026).

Each password holds only the role and permissions of the user it belongs to. A password made for an editor can do what an editor can do, and nothing more, because WordPress still checks that user on every request.

The password is stored hashed in WordPress and shown only once, at the moment you create it. Developer.WordPress.org states that it is stored hashed and shown only once at creation time (checked November 2026).

When should you use one instead of your main password?

Use an application password when a tool or script needs to call your site's API on your behalf.

Good uses include a publishing tool that posts drafts, a backup script that pulls content, a mobile app that edits posts, and a reporting tool that reads site data. In each case, the app signs in as one user and does only what that user may do.

Do not use one for logging in through a browser. Developer.WordPress.org states that application passwords cannot be used to log into wp-admin through wp-login.php (checked November 2026).

A guide on how to add two-factor authentication to WordPress covers the right extra step for browser logins, where an application password does not apply.

Use a separate password for each app. If one tool is breached or retired, you revoke only its password and the other tools keep working.

What do you need before you start?

You need a WordPress site on version 5.6 or later, an HTTPS address, and a user account with the role the app needs.

By default, application passwords are available when requests are served over HTTPS. Developer.WordPress.org states that they are available when requests are served over HTTPS, and that availability can be changed with filters (checked November 2026).

Basic Auth sends the username and password encoded in a header, so plain HTTP would expose them on the network. RFC 7617 states that the Basic scheme is not seen as a safe method unless used with a secure system such as TLS (checked November 2026).

Create a dedicated user for the integration when you can. Give it the lowest role that covers the job, such as Editor for a publishing tool or Author for a tool that only writes posts.

A guide on how to add custom user roles in WordPress explains how to shape roles so a tool gets only the permissions it needs.

Check your PHP version too. WordPress.org states that WordPress recommends PHP 8.3 or greater, with HTTPS support (checked November 2026).

How do you create an application password in the dashboard?

Create the password from the user profile screen, name it clearly, and copy it at once because WordPress never shows it again.

Follow these steps:

  1. Log in to wp-admin as the user who needs the credential, or as an admin editing that user.
  2. Open “Users” and then “Profile” for your own account, or “Users”, “All Users”, and “Edit” for another user.
  3. Scroll to the “Application Passwords” section near the bottom of the page.
  4. Type a clear name, such as “Publishing tool” or “Nightly backup script”.
  5. Click “Add New Application Password”.
  6. Copy the password shown and paste it into the app or a safe store right away.

Developer.WordPress.org lists these same steps: log in, open the profile, find the section, enter a name, generate the password, and copy it at once (checked November 2026).

WordPress shows the password in groups of 4 characters for ease of reading. Make WordPress Core states that the password is 24 characters long, made only of upper-case, lower-case, and numeric characters (checked November 2026).

Spaces in the shown password are only for reading. Developer.WordPress.org states that the password can be used with or without the spaces, because spaces are stripped before checking (checked November 2026).

If you close the page before copying it, do not search for it. Delete that entry and create a new one with the same name.

How do you use it with the REST API?

Send the username and the application password with HTTP Basic Auth on a request to the REST API over HTTPS.

The client sends the credentials in an Authorization header. Developer.WordPress.org states that the header value is made by Base64-encoding the string username:password (checked November 2026).

A simple check with curl reads your own user record:

curl --user "USERNAME:APPLICATION_PASSWORD" https://example.com/wp-json/wp/v2/users/me

Replace USERNAME with the WordPress login name, APPLICATION_PASSWORD with the 24-character password, and example.com with your own domain. A working call returns your user data as JSON.

Developer.WordPress.org gives this same curl example against the /wp-json/wp/v2/users/me route (checked November 2026).

RFC 7617 states that the Basic scheme sends a user-id and password pair encoded with Base64, and that the user-id and password are joined with one colon before encoding (checked November 2026).

A guide on how to create a custom REST API endpoint in WordPress shows how your own routes can use the same signed-in user once the request is authenticated.

MethodWhere the password goesWhen to use it
Dashboard“Application Passwords” sectionFirst setup for one app
curl with --userAuthorization headerQuick checks and scripts
WP-CLICommand line, printed onceServers and automated jobs
Authorize flowauthorize-application.phpLetting a user approve an app

How do you create and manage one with WP-CLI?

WP-CLI can create, list, and delete application passwords from the command line, which suits servers and automated jobs.

The create command has been available since WP-CLI 2.6.0. Developer.WordPress.org states that the command is available since WP-CLI 2.6.0 and takes a user and an app name (checked November 2026).

Create one for user ID 123 with this command:

wp user application-password create 123 "myapp"

Add --porcelain to print only the new password, with no extra text. That form suits scripts that need to capture the value at once.

List the passwords for a user to see names, dates, and last use:

wp user application-password list 123 --fields=uuid,name,created,last_used,last_ip

Developer.WordPress.org gives this list command as the way to show the common fields for a user (checked November 2026).

Delete one password by its UUID when the app no longer needs it:

wp user application-password delete 123 UUID

Store the printed password in a secrets store or an environment variable, never in the repository. A password saved in Git history stays visible to anyone who can read that history.

How do you revoke an application password?

Revoke a password from the same profile section where you made it, and the app loses access at once.

Open the user profile, scroll to “Application Passwords”, find the entry by name, and click “Revoke”. The entry disappears from the list, and later calls with that password fail.

Developer.WordPress.org states that you can review existing passwords by name, see usage data such as last used time and last IP, and revoke single passwords in that section (checked November 2026).

Revoking one password leaves the user's main password and all other application passwords untouched. That is the main gain over sharing a login: one bad tool does not force a password change for everyone.

Make WordPress Core states that the “Last Used” column is correct to within 24 hours, so WordPress writes to the database only when a new day starts (checked November 2026).

Revoke at once if a password leaks, if a tool is retired, or if the “Last Used” data shows use you do not recognize. Then create a fresh password only if the app still needs access.

A guide on how to run a WordPress security audit covers how to review accounts and access after a leak, step by step.

What mistakes should you avoid?

Avoid sharing your main password, reusing one password across apps, and saving the password where other people can read it.

Never paste your main WordPress password into a third-party tool when an application password will do. The main password opens wp-admin, while the application password works only for API calls.

Do not reuse one application password for two tools. Developer.WordPress.org advises one password per integration, and to revoke any credential that is no longer needed (checked November 2026).

Do not send the password over plain HTTP. Because Basic Auth credentials can be read on the network when sent without encryption, always use HTTPS for API calls.

Do not give the app an admin account when an editor account would do. A publishing tool with admin rights can change settings, install plugins, and edit users, which a publishing job never needs.

Do not turn the feature off by accident. Developer.WordPress.org states that security plugins, must-use plugins, or custom code may disable application passwords through filters (checked November 2026).

How do you check that it worked?

Check the password with a read-only API call, then confirm the “Last Used” data shows the new activity.

Run the curl call to /wp-json/wp/v2/users/me from the earlier section. A 200 response with your user record means the password, the username, and the HTTPS setup all work.

A 401 response means the credentials were wrong or the password was typed with an error. Check the username spelling first, then make a fresh password if the copy still fails.

A 403 response means the user signed in but lacks the permission for that route. Check the user role, and use a route the role may use, such as reading your own profile.

If the “Application Passwords” section is missing from the profile, check three things: the site runs WordPress 5.6 or later, the site uses HTTPS, and no plugin or code has disabled the feature.

A guide on how to fix the REST API error in Site Health covers the checks to run when API calls fail for other reasons, such as a blocked route or a failing loopback request.

Frequently asked questions

Can I log into wp-admin with an application password?

No. Application passwords work only for API calls, such as the REST API and XML-RPC. They cannot log anyone into wp-admin through wp-login.php, so browser logins still need the main password, ideally with two-factor authentication turned on.

Can I see an application password again after I create it?

No. WordPress stores the password hashed and shows the clear text only at creation. If you lose the copy, revoke that entry from the user profile and create a new application password with the same name.

Do application passwords work on any WordPress site?

Yes, if the site runs WordPress 5.6 or later and uses HTTPS. By default the feature is available on HTTPS sites. A security plugin or custom code can disable it with the wp_is_application_passwords_available filter.

Should I make one password for all my tools?

Make one password per app and name each one clearly. That way you can revoke a single tool without touching the others, and the Last Used data shows which tool used the site and when.

What should I do if an application password leaks?

Revoke the password from the user profile at once, then check the Last Used data for odd activity. Create a fresh password only if the app still needs access, and review the user role so the app holds the lowest role that covers the job.

Why does my API call return 401 or 403?

A 401 means the username or password was wrong, so check the spelling and make a fresh password if needed. A 403 means the sign-in worked but the user role lacks permission for that route, so check the role or use a route the role may use.

Sources

  1. Application Passwords WordPress Developer Resources
  2. Application Passwords: Integration Guide Make WordPress Core
  3. wp user application-password create WordPress Developer Resources
  4. RFC 7617: The Basic HTTP Authentication Scheme IETF
  5. Requirements WordPress.org
  6. Authentication (REST API Handbook) WordPress Developer Resources

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.