Field Forge: WordPress Custom Fields Plugin. Values in a table of their own.
A custom fields plugin for WordPress that keeps its values in a table of its own.
35 field types
Custom table storage, an ACF compatibility layer, AI schema generation, and TypeScript and GraphQL generation (Pro).
Basic
text, textarea, number, range, email, url, password, calculation
Content
image, file, wysiwyg, oembed, gallery
Choice
select, checkbox, radio, true/false, button group
Relational
relationship, post object, page link, taxonomy, user, link
jQuery
date picker, time picker, color picker, google map
Layout
tab, accordion, message
Pro compound
repeater, group, flexible content, clone
PHP Blocks (Pro)
PHP-rendered Gutenberg blocks. A Pro feature, not a field type.
Calculation & totals
Formula fields, repeater line-item sums (with the Pro Repeater), and cross-post totals by shortcode, PHP helper and REST. The GraphQL query is Pro.
35 field types. One builder.
From a plain text field to a repeater: 35 field types, four of them Pro.
Define your data model once. Read the values in PHP and over REST; with Pro and WPGraphQL, over GraphQL too.
Read your fields in PHP, over REST or in GraphQL.
Read field values in PHP with get_field(), over the REST API, and, with Pro and WPGraphQL, over GraphQL.
query { post(id: 42) { title fields { hero price gallery } } }
How Field Forge works
Install the plugin, define your fields, use them in your theme.
Custom table storage
WordPress keeps custom field values in the wp_postmeta table by default. Field Forge keeps its field values in a table of its own, wp_fieldforge_values. get_field() reads the top-level values of a post with one query and caches them with the WordPress object cache API.
ACF compatibility layer
Field Forge defines these ACF template functions: get_field(), the_field(), get_fields(), have_rows(), the_row(), get_sub_field(), get_row_index(), get_row_layout(), update_field(), delete_field(), get_field_object(), and others. It also defines acf_register_block_type() for PHP-rendered Gutenberg blocks.
AI schema generation (Pro)
Describe the field group you want in plain English, and Field Forge builds it. "Hero section with title, subtitle, background image, and CTA button" → two field groups, Hero Section and Call to Action, built from the matching templates with typed fields and defaults. Field Forge ships with 25 built-in templates (hero, FAQ, testimonials, features, pricing, team, CTA, gallery, contact, product, SEO, quick links and more) and falls back to an AI call for custom descriptions.
Headless WordPress
With Pro, the Headless Types panel generates TypeScript type definitions (.d.ts) and GraphQL SDL from your field groups when you press Generate TypeScript or Generate GraphQL. When WPGraphQL is active, Field Forge registers its field types with WPGraphQL. The types are for JavaScript frontends such as Next.js, Astro or Nuxt that use WordPress as a CMS.
Pricing
Every plan includes all 35 field types, custom table storage, the ACF compat layer, AI schema generation, TypeScript and GraphQL generation, the visual builder, local JSON sync and schema versioning.
Frequently asked questions
Field Forge defines the common ACF template functions (get_field(), the_field(), have_rows(), and others) and acf_register_block_type() for PHP blocks. Theme code that calls these functions keeps working after migration.
ACF is listed on WordPress.org by WP Engine and shows 2+ million active installations there (October 2026). Secure Custom Fields (SCF) is listed there by WordPress.org and shows 100,000+ active installations (October 2026). Field Forge is a separate plugin with its own storage (custom table, AI features, TypeScript/GraphQL) and an ACF compatibility layer for theme code written for either. Read the guide →
Gutenberg and WPGraphQL yes, Elementor not directly. Field Forge has no Elementor integration (no dynamic tags): an Elementor page shows its values through template or shortcode code that calls get_field(). Gutenberg custom blocks can use get_field() in render callbacks. With PRO, Field Forge registers its types with WPGraphQL when WPGraphQL is active.
Yes. The ACF importer copies your field groups into Field Forge’s own storage, then copies the existing field values in batches. After you have checked the result, you deactivate ACF and Field Forge takes over. Theme code that calls the ACF template functions needs no change.
No. AI requests go to our AI backend (api.avakode.com), which passes it to the AI provider; section 3.4 of the Privacy Policy says what the backend logs. Your first paid Forge activation grants the shared welcome credit pack once per account, and you can buy non-expiring top-up packs when needed.
Yes. Field Forge Free is on WordPress.org with unlimited field groups, 31 field types (including relationship, post object, taxonomy, and user), the visual builder, location rules, the ACF compatibility layer, Local JSON sync, ACF field-value migration, and field values on the WordPress REST API. Paid plans unlock AI, TypeScript/GraphQL, the compound field types (repeater, flexible content, group, clone), and options pages.
Ready to try Field Forge?
14-day refund. An importer for ACF and SCF field groups and values. No importer for Meta Box, CMB2, Carbon Fields, Pods or Toolset.
One forge. Twelve tools. One fire.
Every tool is forged in the same workshop — one AI engine, one design language, one account. Take more off the wall and the whole set gets cheaper.