Find WordPress User IDs

Instructions

1. Enter the website domain — type the URL of the WordPress site you're interested in into the field above. A bare domain like example.com is enough; https://example.com and a trailing slash both work too.
2. Click "Find User IDs" — the tool reads the site's users straight from its WordPress REST API.
3. See the results — you get a count and a table of every user returned, with its ID, name, and slug.

This is the easiest way to find user IDs for a given WordPress site. There's no login, no API key, and no plugin to install — the request goes from your browser directly to the site's public API, so nothing passes through a server here.

What you get back

The results table lists three columns for each user:

One thing worth knowing: an anonymous request to this endpoint returns published authors only — users who have at least one published post in a public post type. Subscribers, contributors who've never published, and admins who don't write are not exposed to a logged-out request, by design. So the count you see here is the site's author list, not its full user table. The tool requests up to 100 users in a single call.

Where the IDs come from

The tool calls the site's core REST endpoint:

https://example.com/wp-json/wp/v2/users?per_page=100

That endpoint is part of WordPress core and is open to anonymous, cross-origin requests by default, which is why this works from your browser without a proxy. You can open that URL yourself and read the raw JSON — the tool just normalizes the domain you type, requests the list, and renders the fields worth reading.

When it doesn't work

The tool requires a functioning WordPress REST API. If it can't get a usable list, it tells you which of these it hit:

• The site blocks its REST API. Some hosts, security plugins, and firewalls return a 401 or 403 for anonymous API requests. Disabling the users endpoint specifically is a common hardening step, so this one fails more often than the tag and category lookups do.
• No REST API was found at that address. Either the URL isn't a WordPress site, or the address is wrong. A site that serves an HTML page where JSON should be lands here too.
• The response wasn't readable. The site responded, but not with the JSON list a standard WordPress API returns.
• The site couldn't be reached. Usually a typo in the domain, or a connection problem.

Always remember your user ID

User IDs are a big part of WordPress, but they are a hassle to remember. They are used to assign permissions and display content tailored to specific users. When configuring plugins, user IDs help manage settings and preferences, ensuring notifications reach the right users. Having user IDs simplifies bulk user management tasks, like updating roles, deleting multiple users, or exporting data. They are also essential for running precise database queries to find or update user-specific information — author, author__in, and author__not_in in a WP_Query all take IDs, and so does get_userdata().

From a security perspective, user IDs help track changes, monitor activities, and implement effective security measures. They are crucial in API interactions, ensuring accurate data handling. A display name can be changed at any time and an author slug can be rewritten, but the ID is assigned once and never moves, which is what makes it the reliable key for audit logs, content audits, and author migration maps. Lastly, knowing your user ID helps personalize your experience on the site based on individual preferences.

I hope this helps simplify your WordPress management.

You also might find the WordPress Category ID finder and WordPress Tag ID finder useful.