19 field types
Text, choice, media, relationship and structural types — including nested groups and repeaters — cover the field-group patterns a real site actually needs.
Oiko / plugins / fields
Custom fields
Oiko Fields
A free, secure-by-default alternative to ACF and Meta Box — 19 field types, options pages and conditional logic, with a template API close enough to ACF's own that most ACF-authored theme code keeps working.
free forever · no pro tier · no ads · nothing phones home
Price£0 — full feature set
Field types19, incl. repeater & group
Template APIACF-compatible
REST exposureoff by default, per field
Release gateWP HealthKit audit
Free where others chargeOptions pages and conditional logic ship free here — ACF gates one behind Pro, Meta Box gates both behind paid extensions.
ACF-compatible, not ACF-adjacentget_field(), have_rows(), the_row() and get_sub_field() match ACF's own call signatures, so existing theme code mostly keeps working.
Nothing exposed by defaultEvery field's REST meta registration ships with show_in_rest set to false until you opt a field in.
Itself auditedEvery tagged release passes WP HealthKit's own scanner before it publishes.
What it does
Everything a field-group builder needs, none of it gated.
The two things ACF and Meta Box hold back for a paid tier — options pages and conditional logic — ship free here, alongside everything else a field-group builder needs.
Options pages, free
A field group with no post attached becomes a top-level or submenu settings page under its own values — no separate extension, no separate purchase.
Conditional logic, free
Show or hide a field based on another field's current value. Meta Box sells this as a paid extension; here it ships in the box.
An ACF-compatible template API
get_field(), have_rows(), the_row() and get_sub_field() match ACF's own signatures closely enough that most ACF-authored theme code keeps working unmodified.
Field-group JSON export/import
Export a field group's definition as a portable JSON file; re-importing the same file updates the matching group instead of creating a duplicate — version-controllable, ACF Local JSON-style.
Location rules
Attach a field group to a post type, page template, taxonomy term or user role — the same location-rule shape ACF users already expect.
Privacy-first REST defaults
Every registered field meta key defaults to show_in_rest => false. A field's data is never unintentionally exposed over the REST API — you opt a field in, never out.
GDPR export & erasure
Wired into WordPress's own personal-data export and erasure tools for any field group attached to a user.
Why it exists
The wedge ACF and Meta Box won't ship free.
ACF's 2023 acquisition by WP Engine left plenty of developers weighing alternatives. Meta Box — the tool many of them already reached for instead — still paywalls options pages and conditional logic as separate paid extensions. ACF gates options pages behind its own Pro tier. Oiko Fields ships both free, on purpose.
That's the same standard every Oiko plugin ships to: the full feature set, free, because the point is proving what the standard looks like — not taste-testing a paid tier.
- 01Options pages — a paid extension in Meta Box, Pro-gated in ACF — ship free here.
- 02Conditional logic — a paid Meta Box extension — ships free here too.
- 03Every field's REST exposure defaults to off, not on-and-hope-nobody-notices.
- 04Field-group definitions export as portable JSON, matched on re-import by a stable key.
Built the Oiko way
oiko-plugin-boilerplatePHP 8.3+ · WP 6.7+PHPUnit + WP_MockPHPCS / PHPStan cleanshow_in_rest false by defaultGDPR export & erase
Questions
Fair ones.
Will my ACF theme code just work?+
Most of it. get_field(), have_rows(), the_row() and get_sub_field() match ACF's own call signatures, so theme code written against ACF typically keeps working unmodified. Field-group definitions themselves still need recreating in Oiko Fields' own builder — there's no one-click ACF import yet.
Why free, when ACF and Meta Box charge for this?+
Options pages are Pro-gated in ACF; conditional logic is a paid extension in Meta Box. Oiko Fields ships both free, the same way every Oiko plugin ships its full feature set free — the standard is the product.
Is any field data exposed over the REST API?+
No, not unless you explicitly opt a field in. Every field's REST meta registration defaults to show_in_rest => false.
Also free