An ACF developer for content modelling, field group architecture, flexible layouts, and ACF Blocks. Including a straight answer on ACF versus Secure Custom Fields.
An ACF developer designs the content model first, then builds field groups, flexible layouts, and ACF Blocks around it, so editors get structured inputs rather than a blank WYSIWYG. Rates start at 15 USD per hour, this work is usually part of a larger build, and the current live question is whether you should be on ACF or the Secure Custom Fields fork.
Hiring an ACF developer starts with what the plugin is for. Advanced Custom Fields turns WordPress from a blogging tool into something you can model real content in. Instead of asking an editor to paste a layout into a WYSIWYG box and hope, you give them labelled inputs that produce structured data, and the template decides how that data renders.
The part people underestimate is that an ACF developer spends more time deciding than building. What should be a post type, what should be a taxonomy, what should be a field, and what should be a relationship. Get that wrong and no amount of field configuration saves you, because you will be fighting the model every time the content changes.
The plugin an ACF developer works with is mature and well documented. The official ACF resources cover field types and the API properly, and because ACF stores values in standard WordPress post meta, anything built with it stays readable by other code rather than locked into a proprietary format.
I work as an ACF developer on the majority of custom builds I take on, across a large share of my 250+ projects. Some of that is greenfield modelling. A good deal is inheriting a site where somebody created forty fields, used eleven, and documented none.
A decision every ACF developer now has to walk clients through, without taking sides.
In October 2024, WordPress.org forked Advanced Custom Fields into a separate plugin called Secure Custom Fields, as part of a wider dispute with WP Engine. That fork is still in place. ACF continues as a commercial product from WP Engine, updating from their own servers rather than the WordPress.org directory, while Secure Custom Fields is maintained as its own project. Both are actively shipping releases, and the underlying dispute remains unresolved.
Practically, three things matter when choosing an ACF developer and a plugin. First, they are now different plugins that share a history, and installing one deactivates the other, so this is a choice rather than an upgrade path. Second, ACF no longer updates through the WordPress.org directory, which means a site configured incorrectly can silently stop receiving updates including security fixes. Third, the two projects differ at the Pro feature tier, and published comparisons genuinely contradict each other on exactly which features SCF includes.
So the advice an ACF developer should give is unglamorous. If you already run ACF Pro and updates are arriving, staying put is perfectly reasonable. If you are starting fresh with simple field needs, either works. If you depend on Repeater, Flexible Content, or Options Pages, check the current release of whichever you are considering rather than trusting an article, because this is the exact point where sources disagree and where being wrong costs you a rebuild.
What I will not do as an ACF developer is tell you one side of a commercial dispute is morally correct. You need a site that works and receives security updates. That is a technical question with a technical answer, and it takes ten minutes on a call. Related work under security hardening and maintenance plans.
Six kinds of work that make up most ACF developer engagements.
Deciding what should be a post type, a taxonomy, a field, or a relationship before any field group is created. The decision that determines whether the site is maintainable later.
Groups scoped by location rules, sensible field keys, conditional logic, and validation, so editors see only what applies to what they are editing.
Modular page building where an editor assembles sections from defined components, with the structure locked so layouts cannot be broken.
Custom Gutenberg blocks registered with PHP templates rather than a React build pipeline, giving structured editable components without JavaScript tooling.
Fields rendered efficiently in themes and builders, queried together rather than one at a time, with escaping handled properly.
Restructuring field data without losing it, written as tested scripts run against a copy of the real database rather than a hopeful rename.
Usually part of a larger engagement: WordPress development, custom themes, or custom plugins.
Two or more of these, and an ACF developer will save you more than the engagement costs.
Send me admin access or a screenshot of your plugins page. I will tell you which you are running, whether updates are actually arriving, and whether your field structure is doing you any favours.
Get a Free Site ReviewFour principles behind every ACF developer engagement I take on.
The temptation is to open the field group editor and start adding things, and it is the mistake that separates an ACF developer from someone who has used ACF. An ACF developer who does that produces a site that works on launch day and becomes unworkable as the content grows, because nobody decided what the things actually are.
So the first conversation with an ACF developer should be about entities and relationships. Is a case study a post type or a page? Are service categories a taxonomy or a select field? Does a team member belong to one office or several? Those answers determine your URL structure, your archive pages, and what is queryable, and changing them later means migrating data rather than editing a setting.
Taxonomies are better than a select field for categorisation, because they bring archive pages, query support, and admin filtering without any code. Post types are better than a field flag distinguishing content kinds. A good ACF developer reaches for the platform first and the plugin second.
Fields are for attributes of a thing: a price, a subtitle, a set of images, a repeating list of specifications. When a field starts being used to categorise or relate, that is usually a signal the model needs revisiting rather than another field.
ACF stores values in standard post meta, which an ACF developer should treat as a strength for interoperability and a trap for performance if you are careless. Twenty separate field calls on a page are twenty lookups unless they are fetched together, and filtering a query by meta value across a large dataset gets slow in a way that surprises people.
The fixes are ordinary: fetch groups together, cache what is expensive, and where you are querying by a value constantly, consider whether it should be a taxonomy instead. Detail under speed optimisation and bug fixing.
Renaming a field key does not move the data underneath it, it orphans it, and this is where an inexperienced ACF developer does real damage. Restructuring content therefore means writing a migration that reads the old structure and writes the new one, then running it against a copy of the real database and checking the output before it goes near production.
This is the part where inherited sites cause the most damage, because whoever renamed a field two years ago left content nobody can see and nobody knows is missing. An ACF developer should be documenting field purposes at handover for exactly this reason. Related work under migration services.
Four ways to engage an ACF developer, though this work most often sits inside a larger build.
| Model | Suits | How it works | Typical timeline |
|---|---|---|---|
| Content model design | A new build or restructure | Model first, then field groups and templates | One to two weeks |
| Part of a full build | Most projects | Included in the fixed-price build quote | Within the build |
| Field data migration | Restructuring existing content | Scripted, tested on a database copy | Days to two weeks |
| Maintenance plan | Ongoing changes and updates | Tested updates plus development hours | Monthly, ongoing |
Rates start at 15 USD per hour, though most work is quoted fixed-price. Any ACF Pro or equivalent licence is bought directly by you and is not part of my fee.
ACF developer cost, the SCF fork, Pro features, performance, blocks, and data migration.
The ACF and Secure Custom Fields situation described here reflects the position as of the update date above. Both projects continue to ship releases and the underlying dispute is unresolved, so verify the current state before making a decision that is expensive to reverse.
Free 30-minute call. Tell me what your content actually is and who edits it, and you get a fixed-price quote within 48 hours. Including a straight answer on ACF versus SCF for your situation.
