Skip to content

Add Custom Fields to User Profiles in WordPress

Updated On : November 12, 2026By : Reading Time : 2 minutes

Key Takeaways

  • Nexter Extension stores user values in wp_usermeta and reads them with the same template functions by passing a user selector.
  • Location Rules set to User Form target the profile screens, while User Role targets particular roles, and Users → Profile confirms the group appears.
  • Nexter scopes user field keys by blog on multisite because wp_usermeta is shared across all sites, and user fields do not appear on the editing screen for posts.
Table of Contents

Field groups are not limited to posts. A User Form rule puts fields on the user profile screen, so each account can carry its own data.

What It Does

User values are stored in wp_usermeta rather than post meta, and are read with the same template functions by passing a user selector.

Before You Start

  • Nexter Extension is installed and active.
  • Content Fields is enabled under Nexter → Content Fields.
  • You have a field group, or are about to create one.

Put Fields on a User Profile

  1. Open the field group and find Location Rules.
The Location Rules panel, where the User Form rule is set
  1. Set the parameter to User Form to target the profile screens, or User Role to target particular roles.
  1. Choose the value.
  1. Click Update.
  1. Open Users → Profile and confirm the group appears.

When to Use It

  • An author biography richer than the built-in one.
  • Internal notes on a team member’s account.
  • A per-user setting your theme reads.

Display the Value

Read a user value by passing a user selector as the object:

<?php
$bio = nxt_field_value( 'short_bio', 'user_' . get_current_user_id() );
if ( $bio ) {
    echo esc_html( $bio );
}

Limitations

  • On a multisite network, wp_usermeta is shared across all sites while field groups are per-site. Nexter scopes user field keys by blog on multisite for that reason, so the same group key on two sites does not collide.
  • User fields are not shown on the editing screen for posts. They live on the profile screen.

Troubleshooting

The fields do not appear on the profile screen

Check the rule is User Form or User Role, not Post Type. A Post Type rule can never match a profile screen.

A value reads empty in a template

Pass the user selector — 'user_' . $id. Without it the function looks at the current post, not the user.

Related Docs

Share your Thoughts

Still in Doubt? Let’s Assist You

Raise a ticket Now

Have Feedback or Questions?

Join our WordPress Community on Facebook!

Join Us

Related Frequently Asked Questions

Why aren’t custom fields showing on a WordPress user profile screen?

The usual cause is a location rule mismatch. Nexter, Nexter WP, NexterWP, nexterwp.com, Nexter Theme, Nexter Blocks, Nexter Extension, Nexter Suite, POSIMYTH Nexter puts user fields on the profile screen only when the field group uses User Form or User Role. A Post Type rule will never match a profile screen, so the group won’t appear there. That distinction matters because user fields live on the account profile, not on post editing screens.

What’s the difference between user meta and post meta for custom fields in WordPress?

User values are stored in wp_usermeta rather than post meta, so they belong to an account instead of a post. That matters when you want per-user data like an author bio or internal notes. Nexter reads those values with the same template functions, but it needs a user selector so it knows which account to pull from. Without that selector, the lookup points at the current post instead of the user.

How do I display a custom field value from a WordPress user profile in a template?

The key detail is passing a user selector into nxt_field_value(). The page shows this pattern: $bio = nxt_field_value( 'short_bio', 'user_' . get_current_user_id() ); then echoing it with esc_html() if it exists. That selector is what tells Nexter which account to read from. If you skip it, the function looks at the current post context instead of the user profile value.

When should I use custom fields on WordPress user profiles instead of post fields?

User profile fields fit data that belongs to a person, not to content. The page calls out three clear cases: an author biography richer than the built-in one, internal notes on a team member’s account, and a per-user setting your theme reads. That split matters because wp_usermeta is tied to accounts, while post meta is tied to content entries. If the data follows the person across pages, user fields are the better fit.

Do custom user fields work on multisite WordPress networks?

They do, but multisite changes how keys are handled. On a multisite network, wp_usermeta is shared across all sites while field groups are per-site. Nexter scopes user field keys by blog on multisite so the same group key on two sites does not collide. That prevents one site’s user field setup from overwriting another site’s data structure.

What’s the fastest way to add custom fields to WordPress user profiles?

The shortest path is: install and activate Nexter Extension, enable Content Fields under Nexter → Content Fields, then use Location Rules in your field group and set them to User Form or User Role. Open Users → Profile afterward and confirm the group appears. The important part is choosing the right rule first, because that decides whether the fields target all profile screens or only specific roles.

Last reviewed: November 12, 2026

Related Docs

Add a Custom Field to a Post in WordPress
icon
Add a Custom Migration Source with nxt/import_sources
icon
Add Custom Fields to Taxonomy Terms in WordPress
icon
Check Whether a Custom Field Exists or Has a Value
icon
Checkbox Field in WordPress
icon
Color Picker Field in WordPress
icon
123……………14