Works With Your Stack

Field Forge isn’t a silo. Your WordPress site already runs a specific stack — a page builder, a block editor, an e-commerce platform, a headless frontend. Field Forge has first-class integrations with all of them so custom fields work wherever you need them.

---

WPGraphQL

Native auto-registration of GraphQL types for every field group. When Field Forge and WPGraphQL are both active, custom fields become queryable via GraphQL automatically — no separate plugin, no manual schema registration.

Full WPGraphQL integration →

---

Elementor

Native Dynamic Tags integration. Field Forge field values are available as dynamic sources in every Elementor widget. Works with Elementor free and Elementor Pro’s Theme Builder. Repeater fields integrate with Loop Grids (Elementor Pro).

Full Elementor integration →

---

Gutenberg

Field groups render as metaboxes in the block editor. Custom Gutenberg blocks can use acf_register_block_type() (ACF-compatible) with PHP render callbacks that access Field Forge values. Auto-detection of FAQ blocks for structured data generation.

Full Gutenberg integration →

---

WooCommerce

Custom fields on products, variations, orders, and customers. Supports repeaters, flexible content, and all 32 field types on WooCommerce content. Performance-optimized via custom table storage for large product catalogs.

Full WooCommerce integration →

---

Page builders (beyond Elementor)

Divi

Field Forge values are accessible in Divi via Dynamic Content. Add fields to modules, read custom fields in Divi Theme Builder templates.

WPBakery Page Builder (Visual Composer)

Custom field shortcodes can reference Field Forge values. Integration with WPBakery’s Grid Builder for dynamic content.

Beaver Builder

Beaver Themer reads Field Forge field values via standard get_field() calls in PHP-based connections.

Oxygen Builder

Oxygen’s dynamic data feature pulls Field Forge values natively.

Bricks Builder

Bricks Builder’s dynamic data system reads Field Forge field values via the standard WordPress meta API.

All of the above work because Field Forge’s storage exposes field values via standard WordPress hooks and functions. Page builders that support custom fields support Field Forge.

---

Headless WordPress frameworks

Next.js

REST API or GraphQL consumption, TypeScript type safety via auto-generated .d.ts, example integration code available.

Astro

Works with Astro’s WordPress fetching patterns. TypeScript support. Works with Astro Islands architecture.

Nuxt

Vue-based frontend, consumes Field Forge via REST API or WPGraphQL + Nuxt Content.

SvelteKit

Svelte-based frontend with WordPress as CMS. Built-in TypeScript support.

Remix

React-based server-first framework. Works with Field Forge via REST API or GraphQL.

Gatsby

Static site generator with WordPress as CMS. Integrates via gatsby-source-wordpress plugin which reads Field Forge REST API responses.

For any headless framework, Field Forge’s TypeScript generation, GraphQL integration, and REST API cover the common use cases.

---

ACF-compatible plugins

Field Forge’s ACF compatibility layer means most plugins that integrate with ACF also work with Field Forge:

• WPGraphQL for ACF — use Field Forge’s native WPGraphQL integration instead
• ACF Extended — many features available natively in Field Forge
• ACF Frontend Form — use Form Forge (our separate form plugin) for the same use case
• Third-party plugins that read get_field() and have_rows() calls — work transparently

If a plugin only uses ACF’s public template functions, Field Forge’s compat layer handles it.

---

Forge Suite cross-plugin integration

Field Forge is part of Forge Suite, a bundle of four WordPress plugins built by the same team:

Lang Forge (multilingual)

Field Forge field values are translatable via Lang Forge. Create field groups once, translate values in Lang Forge’s editor. Lang Forge auto-registers Field Forge fields as translatable strings.

SEO Forge (SEO optimization)

SEO Forge auto-detects FAQ blocks built with Field Forge Repeater fields and generates FAQ schema automatically. Field Forge values are available as dynamic variables in SEO Forge’s title and description templates.

Form Forge (form builder)

Form Forge can post submissions to custom post types with Field Forge custom fields. Create a field group for form submissions, then map Form Forge form fields to Field Forge custom fields for structured storage.

Forge Dashboard

When multiple Forge Suite plugins are active, a unified dashboard appears showing field groups, SEO scores, translation status, and form stats in one place.

---

Third-party plugin compatibility

Custom post types

• CPT UI — Field Forge location rules match custom post types registered by CPT UI
• Pods — can coexist, field data stored separately
• Toolset Types — Field Forge can import Types field groups

Page builders

• All major page builders work via get_field() or Dynamic Data features

Headless plugins

• WPGraphQL — native auto-registration (covered above)
• WP REST API Controller — works with Field Forge’s REST API exposure

Caching plugins

• WP Rocket — Field Forge’s object cache integration works with WP Rocket’s cache layer
• W3 Total Cache — same
• LiteSpeed Cache — same
• Redis Object Cache — Field Forge uses it natively

Backup plugins

• UpdraftPlus — Field Forge’s custom table is included in full-database backups automatically
• BackWPup — same

---

Don’t see your plugin?

If you’re running a plugin not mentioned here and want to know if it works with Field Forge, contact support. Most plugins that work with ACF also work with Field Forge via the compatibility layer. For anything custom, we can usually confirm or provide a workaround.

---

Ready to integrate Field Forge with your stack?

Get Field Forge — from $35/year →

Every integration above is included in every plan — free and paid. (Headless tooling like native WPGraphQL types, TypeScript/GraphQL generation, and PHP blocks is part of the paid plans.)