Field Forge vs Carbon Fields — Code-First Alternative

Carbon Fields is a free, open-source WordPress custom fields library maintained by HTML Burger. Like CMB2, it’s a code-first library where developers define fields in PHP rather than using a visual builder. It has a loyal following among experienced WordPress developers who prefer programmatic field setup, and it’s lightweight and performant for its use case.

But Carbon Fields has no visual builder, no paid support, no AI features, and an effectively invisible organic search footprint (13 keywords, 40 monthly traffic per SEMRush data). For teams that want both code-first workflows AND visual editing, Field Forge is the better fit.

---

TL;DR comparison

---

Where Carbon Fields is strong

Excellent developer API

Carbon Fields has one of the cleanest code APIs in the WordPress custom fields space. Field registration uses fluent method chaining that reads naturally:

use Carbon_Fields\Container;
use Carbon_Fields\Field;

Container::make('post_meta', 'Hero Section')
    ->where('post_type', '=', 'page')
    ->add_fields([
        Field::make('text', 'hero_title', 'Hero Title'),
        Field::make('textarea', 'hero_subtitle', 'Hero Subtitle'),
        Field::make('image', 'hero_image', 'Hero Image'),
    ]);

For developers who value clean PHP code, Carbon Fields feels more elegant than CMB2’s older-school API.

Free and open source

GPL-licensed, free forever, maintained by HTML Burger (a WordPress development agency). No subscription, no license keys.

Lightweight

Small codebase with minimal runtime overhead. No heavyweight admin UI to render because there’s no admin UI beyond the standard post meta box rendering.

Maintained by an active agency

HTML Burger is an active WordPress development agency that uses Carbon Fields internally on client projects. This gives Carbon Fields a level of maintenance continuity that purely hobbyist projects sometimes lack.

---

Where Field Forge wins

Visual builder

The core trade-off is the same as with CMB2: Carbon Fields has no visual builder. Every field must be defined in PHP code. For teams that include non-developers, or developers who want to rapid-prototype field group structures before committing to code, Carbon Fields requires switching to a different tool.

Field Forge offers both a visual builder AND a code API. Developers can use the code API for production deployments; non-developers can use the visual builder; content editors can view and edit field groups without touching PHP.

Visual builder feature →

AI schema generation

No other custom fields plugin has AI-based field group generation. Field Forge is first. For teams building new field groups regularly, AI generation saves significant time over hand-coding every field.

AI schema generation feature →

Custom table storage

Carbon Fields stores values in wp_postmeta, same as ACF and CMB2. Performance on large sites is the same (or similar to) ACF — the N+1 query problem affects all wp_postmeta-based plugins equally.

Field Forge’s custom indexed table is 3–10x faster on sites with 1,000+ posts or complex repeaters.

Custom table storage feature →

ACF compatibility layer

Carbon Fields has its own API and doesn’t try to be ACF-compatible. Migration from ACF to Carbon Fields requires rewriting every template reference. Migration from Carbon Fields to ACF or any other plugin requires the same rewriting.

Field Forge’s ACF compatibility layer means Carbon Fields code can be gradually migrated: you can mix Field Forge and Carbon Fields during transition, and once migrated, your get_field() calls work natively.

ACF compatibility layer feature →

Headless WordPress tooling

Carbon Fields has no TypeScript generation, no GraphQL schema output, and no WPGraphQL integration. For headless WordPress teams using Next.js / Astro / Nuxt, Carbon Fields means writing types by hand or using a separate GraphQL plugin.

Field Forge auto-generates TypeScript and GraphQL definitions for every field group.

Commercial support

Carbon Fields is community-supported via GitHub issues. Response times depend on HTML Burger’s availability, which is secondary to their client work. For production sites that need guaranteed support, community-only isn’t enough.

Field Forge’s paid plans include priority email support with 1 business day response.

Feature-rich pro compound fields

Carbon Fields has complex fields like complex (nested fields) and association (cross-reference). Field Forge has equivalent functionality — Group, Repeater, Flexible Content, Clone, and Relationship fields — with more sophisticated sub-field nesting and a visual builder for configuring them.

---

Migration from Carbon Fields

Carbon Fields migration is currently beta/manual verification scope in Field Forge. Carbon definitions are code-first, so a production move should be handled as a mapped project instead of a guaranteed one-click import:

1. Scan theme/plugin files for Container::make() and add_fields() calls
2. Parse the field configurations into Field Forge’s format
3. Convert container types to Field Forge location rules (post_meta → post type, term_meta → taxonomy, user_meta → user, theme_options → options page)
4. Migrate existing values from wp_postmeta / wp_termmeta / wp_usermeta to Field Forge’s custom table
5. Verify the migration count and spot-check values before deactivating Carbon Fields

What converts cleanly

• Text, textarea, number, email, URL, password fields
• Image, file, WYSIWYG, color picker fields
• Select, radio, checkbox, set fields
• Complex (converts to Group or Repeater)
• Association (converts to Relationship or Post Object)
• Theme options containers (converts to Options Pages)

What requires manual review

• Custom field types registered via Carbon Fields API — may need substitution
• Unusual container configurations (e.g., checkbox containers for conditional visibility) — translate to Field Forge’s location rules manually
• Carbon Fields hooks (carbon_fields_after_save, etc.) — translate to Field Forge’s hook equivalents

Straightforward Carbon Fields sites can usually be planned in hours, but the exact effort depends on custom containers, hooks, and theme API calls.

---

When Carbon Fields is the right choice

• You’re a solo developer who never needs non-dev team members to edit field groups
• You prefer Carbon Fields’ fluent API specifically over other code-first APIs
• Free is a hard constraint and community support is sufficient
• Your site is small (<500 posts) where storage performance doesn't matter
• You explicitly prefer agency-maintained open source (HTML Burger) over commercial products

For everything else — teams with mixed dev/non-dev members, larger sites, headless WordPress, AI features, commercial support — Field Forge is a better fit.

---

Frequently asked questions

Is Field Forge’s code API as clean as Carbon Fields’?

Field Forge’s fieldforge_register_field_group() function uses an array-based configuration similar to ACF’s programmatic API. It’s functional but not as fluent as Carbon Fields’ method chaining. If pure API aesthetic is your priority, Carbon Fields wins on that specific metric. But the trade-off is no visual builder, no AI, no headless tooling, no performance.

Can I keep my Carbon Fields code if I migrate?

Partially. Field Forge’s ACF compatibility layer handles get_field()-style access, but Carbon Fields’ carbon_get_post_meta() function uses a different API. You’ll need to update Carbon Fields data access calls in your theme to use either ACF-style get_field() (via compat layer) or Field Forge’s native API.

Does Field Forge have Carbon Fields’ “complex” field type?

Carbon Fields’ complex field is a repeating field with nested sub-fields. Field Forge has this via the Repeater field type with support for arbitrary sub-field nesting.

Will Carbon Fields work alongside Field Forge during migration?

Yes. Both plugins use different storage (wp_postmeta for Carbon Fields, custom table for Field Forge), so they don’t conflict. Run both during migration, test thoroughly, then deactivate Carbon Fields once the site is fully on Field Forge.

Is Field Forge slower than Carbon Fields on small sites?

No. Field Forge’s custom table storage has equivalent performance to Carbon Fields’ wp_postmeta on small sites. On large sites, Field Forge is significantly faster.

---

Ready for visual building with code-first flexibility?

Get Field Forge — from $35/year →

14-day refund. ACF/SCF one-click import included. Carbon Fields migration is available as beta/manual mapping until a verified importer fixture is complete.