Choose How to Add a Feature

Add WordPress Custom Fields: Native Fields or an ACF Field Group

Add a native WordPress custom field or an ACF field group, then verify its placement and saved values in the Block Editor.

Editorial illustration for How to Add Custom Fields to WordPress Posts: Native Fields or ACF

If you need to add a detail such as a phone number to a WordPress post, use the built-in Custom fields area when a name and value are enough. Choose Advanced Custom Fields (ACF) when editors need a defined group of labeled inputs or a field type such as an image. Both approaches let you set up fields on edit screens; neither step, on its own, makes the values appear on the public page.

Choose the field method by the editing task

A custom field is a key/value pair: the key identifies the detail, and the value contains it. For a hypothetical staff biography published as a regular post, phone could be the key and a test phone number its value. The native interface suits an editor who can enter that name and value directly. It does not require installing ACF for a straightforward detail. This explanation of WordPress custom fields describes the key/value model and the native inputs.

An ACF field group is a better fit when you want to define the inputs before editors use them. For the same biography, you might create a Staff information group containing text fields labeled First name, Last name and Phone. ACF advertises text and image fields for WordPress edit screens, and its location rules control where a group appears. Choose the group for the editing experience you need, not because the phone number will automatically become visible to visitors.

If the requirement is a repeatable set of subfields or an image gallery, account for the edition before planning the layout. The ACF plugin listing identifies Repeater and Gallery as ACF PRO features. They are not prerequisites for the simple text-field group below.

Add a native field in the Block Editor

  1. Open the regular post that should hold the detail. In the Block Editor, open Preferences and enable the Custom fields switcher in the Advanced section. Look for the Custom fields area on the post’s edit screen.
  2. Enter phone as the field name and a test phone number as its value. Select Add Custom Field, then save the post. The native-field walkthrough describes both the switcher and the name/value input.
  3. Reopen that same post. Check that the phone pair is still there and that its value is the one you entered. Checking a different post would not establish that the intended item has the detail.

This is an editor-side check, not a front-end display test. If you cannot see the area in the Block Editor, revisit Preferences → Advanced and check the switcher before assuming the saved field has disappeared. These steps are specifically for the Block Editor; they are not instructions for the classic editor.

Create and target an ACF field group

To try the grouped approach instead, go to Plugins > Add New, search for Advanced Custom Fields or ACF, and install and activate it. Open the new ACF menu and create a field group named Staff information. Add text fields for First name, Last name and Phone. The plugin listing supplies the installation and field-group entry points; ACF’s feature documentation identifies text as an available field type.

Set the group’s location rule to the post type you actually use for staff biographies—Posts in this example—and save the group. ACF says location rules can place fields by post type, among other criteria. If your biographies are pages instead, target pages rather than copying the Posts choice. The point is to match the rule to the content an editor will open.

Now open a staff biography post. Confirm that the Staff information inputs appear there, enter test values, and save the post. Reopen it to check that all three inputs remain populated. If the group is absent, first confirm that you saved it and that its location rule matches the current item’s content type. Seeing the group on an unrelated edit screen would not verify the intended setup.

Keep saved values separate from site display

The checks above establish whether editors can find the fields and whether their test values remain after saving. They do not establish that a theme displays those values. The ACF listing describes functions for loading and displaying values in theme templates, while the native-fields explanation says a theme change is needed before custom fields appear on the site. Treat that display work as a separate theme-integration step. For this setup, success means the native pair or correctly targeted ACF group appears on the intended post and retains its test values when you reopen it.

← All articles

Type at least two characters.

Press <kbd>Esc</kbd> to closeOpen the search page