Advanced Custom Fields (ACF) is a free WordPress plugin, maintained by WP Engine, that lets you attach extra structured content to your posts, pages, users, and more, without touching the WordPress database. In one sentence: it turns the default title-and-body editor into a flexible content system by letting you define fields (text, image, date, relationship, and others) in the admin and then display them in your theme or block.
This guide answers the questions a site owner or junior developer usually asks in order: what ACF actually is, how Free and Pro differ, what field types you get, how to install it and show a field on the front end, when it's the wrong tool, and what it doesn't do on its own. You'll see the exact admin path for your first field group, a plain-English look at the F
The path in 6 steps
The steps of this page, in order.
-
01 Understand what ACF is A plugin that adds custom fields to WordPress content types without editing the database.
-
02 See real use cases Product specs, author bios, event dates, content WordPress doesn't have a slot for by default.
-
03 Compare Free vs Pro Decide whether you need repeaters, flexible content, and ACF Blocks.
-
04 Install and set up Install the plugin, create a field group, and attach it to a post type.
-
05 Display a field Use get_field() and the_field() in your theme to output the value.
-
06 Know when to skip it Recognize the cases where ACF adds overhead without benefit.
01 / 09
What is ACF in WordPress, in plain English?
ACF is a free plugin by WP Engine that lets you add named, structured content fields to WordPress items, posts, pages, users, taxonomy terms, media, comments, and options pages, and then display those values in your theme or block. For the full picture, from hosting and themes to security and SEO basics, see our WordPress guide.
Core WordPress gives every post four slots: a title, a body, an excerpt, and a featured image. A custom field is a named slot you add for anything else, a price, a start date, an author bio. ACF creates those slots through an admin interface, so you never touch SQL or register meta boxes by hand.
ACF is not a page builder and not a block library. It organizes content into fields; how that content appears on the page is still up to your theme, block, or template. Values are stored in WordPress's standard postmeta tables, so content you create today stays readable if you switch themes later.
What ACF adds
Extra content slots for posts, pages, users, taxonomy terms, media, comments, and options pages. A field group is a set of fields ACF shows together in the editor and assigns to one or more content types.
- Makers
- WP Engine
- Price
- Free core plugin
Key pointCheck the field types you need against the official ACF plugin page before installing.
Where it stores data
In WordPress's own postmeta tables, the same place core custom fields live. Values are exposed through a stable PHP API, so they survive most theme changes.
- Storage
- Standard WordPress postmeta
- Access
- PHP API
Key pointExport a database backup before you add your first field group.
Where it sits
Between the block editor and a page builder: it edits the data layer, not the layout. The block editor handles text and media; a page builder handles visual structure; ACF defines what custom content exists.
- Category
- Content modeling plugin
- Not
- Page builder or block library
Key pointDecide the fields first, then pick the theme or builder that renders them.
02 / 09
What kind of content does ACF actually structure?
ACF is most useful when the same page repeats a pattern of extra facts that visitors need to find quickly.
The pattern is always the same: several small facts that belong together, edited in one place, then reused by a template. A field group, the set of fields ACF shows together and assigns to one or more content types, handles each case below.
A location rule decides where that group appears, for example "Post Type is equal to Product". Same idea for authors and events: define the fields once, let the template render them everywhere.
Product specs
A repeater field on each product page, with rows for label and value, so the template loops through specs instead of one long paragraph.
- Field type
- Repeater
- Location rule
- Post Type is equal to Product
Key pointUse one repeater rather than five separate fields you have to duplicate on every product.
Author bios
A small set of profile fields reused on every post that author writes, so the bio stays consistent across the site.
- Field type
- Text, URL, Image
- Location rule
- User Role is equal to Author
Key pointEnter the bio once on the user profile; the post template pulls it in.
Event dates
Start, end and venue fields that an event listing template can sort by date, without touching the post content.
- Field type
- Date Picker, Text
- Location rule
- Post Type is equal to Event
Key pointStore dates as separate fields so the listing can order them; never bury them in the body text.
03 / 09
ACF Free vs Pro: what actually changes?
Free covers the basics, text, image, select, date, and most single-value fields. Pro adds the composite field types that make repeating layouts practical.
Free gives you one value per field: text, image, select, date, and similar types. Pro adds Repeater, Flexible Content, Gallery, Clone, and Options Pages, plus ACF Blocks, a Pro feature that builds custom Gutenberg blocks from ACF fields and a template file.
Pro pays off as soon as the number of rows varies: team members, downloads, pricing tiers. Prices and renewals change, so treat any figure as an estimate until the official ACF pricing page confirms it that day.
Free
- Covers text, image, select, date, and most single-value field types
- No cost, and enough for a simple one-value-per-post setup
- No Repeater, Flexible Content, Gallery, Clone, or Options Pages
- No ACF Blocks for custom Gutenberg blocks
Best for small sites with fixed content.
Pro
- Adds Repeater, Flexible Content, Gallery, Clone, and Options Pages
- Includes ACF Blocks for custom Gutenberg blocks
- Paid license, so check the official ACF pricing page for current cost and renewal terms
- Extra features add setup and maintenance work
Best for growing sites with repeating or flexible content.
Going further
Compare the two
Concept
Repeater vs Flexible Content: which one fits?
Repeater handles a fixed pattern repeated many times; Flexible Content lets editors choose and reorder different layout blocks.
A Repeater is a set of subfields repeated as many times as needed, always in the same order and structure. It fits a team list, a downloads list, or FAQ items where every row looks the same. Editors can add or remove rows, but the shape stays fixed.
Flexible Content goes further: you define several layout types, such as a text block, an image block, or a call-to-action, and editors pick which ones to use and in what order. That freedom suits landing pages and modular sections, but it requires more upfront planning because the template must handle every possible layout.
- Does every row share the same fields?If yes, a Repeater is simpler and faster to build.
- Do editors need to choose between different section types?If yes, Flexible Content gives them that choice without developer help.
- Will the layout change often?Flexible Content reduces future template changes when page structures shift.
- Is the team small?Start with Repeater; only move to Flexible Content when the content truly varies.
04 / 09
How do I install ACF and create my first field group?
The walkthrough is short: install the plugin, open ACF in the admin menu, add a field group, add fields, set a location rule, and publish.
ACF sits under the editor, not on top of it: Gutenberg builds layout and content itself, page builders like Elementor handle layout plus styling, while ACF just adds extra fields. You'll see ACF's fields inside a meta box below the Gutenberg editor, or inside the builder's own editing panel.
Reach for ACF when your content needs a repeating structure your editor or builder doesn't store as data, a list of team members or pricing rows.
-
Install the plugin
In the WordPress admin, go to Plugins → Add New Plugin, search for 'Advanced Custom Fields', then click Install and Activate.
-
Open the field group builder
In the left admin menu, click ACF → Field Groups → Add New. Give the group a clear title.
-
Add your first field
Click Add Field and fill in Field Label (shown in the editor), Field Name (lowercase letters and underscores, used in code), and Field Type (such as Text).
-
Add each remaining field
Use Add Field again for every field you need in this group, so they all appear together.
-
Set the location rule
Under Location, add a rule such as 'Post Type is equal to Post'. That tells ACF where this field group shows up.
-
Publish and check
Click Publish, then open any post for editing. The fields now sit below the editor.
05 / 09
How do I actually display an ACF field on the page?
You read the value in your theme with get_field() (returns it) or the_field() (prints it), and you use the field name you set in the field group.
In your theme, use get_field(), an ACF PHP function that returns a field value, when you need to test or format it before printing. Use the_field(), which echoes the value directly, for plain output. Always wrap printing in a check (for example, if ( get_field('event_date') )) so empty fields don't leave stray labels.
In ACF 6.x, field groups and values are also exposed through the WordPress REST API and the block editor, so a hybrid theme can read the same field in PHP or in a Gutenberg block. ACF also ships shortcodes for quick insertion without touching template files.
-
Pick a template
Choose the theme file that renders the content type you want to change, for example, single-event.php for a single event post.
-
Read the value with get_field()
Call $location = get_field('event_location'); to store the field value in a variable. The first argument is the field name you set in the field group.
-
Print it with a conditional
Check the variable first: if ( $location ) { echo esc_html( $location ); }. This keeps empty fields from leaving labels on the page.
Going further
Show the code path
Method
What a complete snippet looks like
A minimal, safe PHP pattern: get the value, check it exists, escape it, then print.
The snippet below goes inside your theme's template file, where you want the field to appear. It does four things: assigns the field to a variable, checks the variable is not empty, escapes the output for HTML, and prints it inside a wrapper element.
For a URL field, the escape function changes. Use esc_url() instead of esc_html(): if ( $url ) { echo esc_url( $url ); }. For a field that may contain HTML, use wp_kses_post() to allow only safe tags.
If you are working in a block theme, you do not need to edit PHP at all. ACF 6.x exposes fields in the block editor, so you can bind a field value to a block, or use an ACF shortcode such as [acf field="event_date"] inside a paragraph block.
- Field name matchesThe string in get_field() must match the field name in your ACF field group exactly, case-sensitive.
- Value existsWrap output in a conditional so missing values do not print titles, colons, or empty containers.
- Escape outputUse esc_html() for text, esc_url() for links, and wp_kses_post() for rich text.
- Post ID contextInside a loop, get_field() uses the current post automatically. Outside a loop, pass the post ID as the second argument.
06 / 09
What does ACF not do on its own?
ACF manages data, not design. It does not build layouts, does not style anything, and does not guarantee that an old field group still fits a redesigned template.
ACF stores and returns values. How those values look is decided by your theme, block, or page builder. On a site with no custom template, fields exist in the database but never appear on the page.
Renaming a field key orphans the data stored under the old name until you migrate it yourself. And unlicensed copies of ACF Pro sit outside the developer's terms, with no official updates or support.
No layout or styling
ACF returns values; something else has to render them. Without a template, block, or builder that outputs the field, it stays invisible.
- What it gives you
- Data only
- What it needs
- A rendering layer
Key pointTest your template on a staging copy before launch.
No migration on rename
Change a field name and the old value stays attached to the old name. You move the data yourself or it is lost from view.
- Trigger
- Field name change
- Result
- Orphaned values
Key pointBack up the database before renaming a field.
No licence shortcut
Unlicensed or nulled copies of ACF Pro may breach the developer's terms and carry no official updates or support. Those copies are also a common malware carrier.
- Updates
- None
- Support
- None
Key pointGet ACF Pro only from the official Advanced Custom Fields site.
Two listings to check
During the 2024 WP Engine/Automattic dispute, a fork called Secure Custom Fields (SCF) appeared on WordPress.org alongside ACF.
- Fork
- Secure Custom Fields
- Event
- 2024 dispute
Key pointConfirm the plugin author on the WordPress.org page before installing.
07 / 09
Do you actually need ACF?
Install ACF if you have repeating or structured content that WordPress does not model by default. Skip it if your site is a simple blog or is entirely built inside a page builder that already handles the content you need.
Say yes when the same set of attributes repeats across many entries: a product catalog with specs, a staff or location directory, an events calendar, or a portfolio where every project carries the same metadata. Those values belong in fields, not in body copy.
Say no when every page is one-off free-form writing, when a page builder already stores the data you need, or when your only extra content is a hero image and a subtitle. ACF and a builder usually coexist: the builder handles layout, ACF holds values a template or block must reuse.
The same fields repeat across many entries
If you would type the same labels and values on ten or more pages, ACF lets one field group define them once.
No page builder already stores that data
Check whether your builder's own modules or custom fields already hold these values before adding a second system.
You can edit a template or use a block
ACF stores values; something must output them. Confirm you or your developer can edit the theme template or use the ACF block.
You can test on a staging copy first
Field groups change the edit screens and the database. Try the setup on a staging copy before touching the live site.
You will keep the plugin updated
Field data lives in your database, so plan for regular updates and backups as part of normal site maintenance.
08 / 09
What should I do before installing ACF?
Back up the site, check your WordPress and PHP versions, install the free plugin on a staging copy first, and create one field group end to end before rolling it out.
Never install on the live site first. Copy the site to a staging environment, then confirm the plugin's current requirements on a source that actually states them: at the time of writing, ACF 6.8.9 (August 27, 2026) requires WordPress 6.2+ and PHP 7.4+, and is tested up to WordPress 7.1, per the plugin's GitHub release page. If your host runs an older PHP build, ask them to upgrade before you add fields.
Once the staging copy meets those versions, install the free plugin there and prove the whole chain once: create a field group, attach it to a single post type, output it in one template, and check the front end. Only after that single field renders correctly should you repeat the pattern on production.
-
Back up the site
Export a full backup of files and database so you can roll back if anything breaks on the staging copy.
-
Check versions
Confirm your WordPress and PHP versions meet ACF 6.8.9's stated minimums: WordPress 6.2+ and PHP 7.4+, per the plugin's GitHub release page (August 27, 2026).
-
Install on staging
Install the free ACF plugin on a staging copy of the site, not on production.
-
Create one field group
In the WordPress admin, go to ACF > Field Groups > Add New, add a text field called, say, subtitle, and set its location rule to Post Type = Post.
-
Display it in one template
In your theme, use the_field('subtitle') inside the post template, then check the field appears correctly on the front end.
-
Roll out
Once the single field group works end to end, replicate the same pattern for the other post types or pages you need.
09 / 09










