Field Forge integrates with Elementor via the Dynamic Tags system. Every Field Forge field value is available as a dynamic source in Elementor widgets — drop a custom field into any text, image, or button widget with a few clicks, no PHP required. Works with Elementor free and Elementor Pro.
Elementor’s Dynamic Tags system lets widgets pull content from dynamic sources instead of hard-coded values. Instead of typing “Product Name” into a Heading widget, you can select “Dynamic → Custom Field → Product Name” and the widget pulls the value from your current post’s custom field.
This is how Elementor Theme Builder templates work. A single template can render any product page by pulling product name, price, description, image, and features from custom fields dynamically.
Field Forge registers itself as a Dynamic Tag source, making all field groups available to Elementor widgets automatically.
Install Field Forge and Elementor (or Elementor Pro). Activate both. Field Forge detects Elementor on activation and registers its Dynamic Tag source.
Use Field Forge’s visual builder to create a field group and assign it to a post type via location rules. For example:
Edit a product template (or any Elementor page). In any widget’s content field:
Repeat for other fields — drop the Featured Image into an Image widget, the Price into a Price widget, and so on.
Publish the Elementor template. Every product on your site now renders through this template with dynamic field values pulled from Field Forge.
Field Forge exposes these field types as Elementor Dynamic Tags:
Use Field Forge values in Elementor’s display conditions:
Elementor’s Display Conditions (Elementor Pro) read Field Forge values just like any other custom field.
For Elementor Pro users, Field Forge is especially powerful with Theme Builder:
Build one template, render it across hundreds of posts with Field Forge data.
Elementor Pro’s Loop Grid widget can iterate over Field Forge repeater rows:
This replaces what you’d otherwise build with custom PHP and WP_Query loops.
Field Forge options page values are available throughout Elementor via:
Elementor → Site Settings → Custom CSS can reference options page values via CSS variables.
Elementor widgets can pull options page values via Dynamic Tags: select “Field Forge Options → Site Settings → Company Name” instead of “Field Forge → [Post] → Company Name.”
This is useful for global values (site logo, company info, social URLs) that should be consistent across templates.
Field Forge’s custom table storage and object cache integration mean Elementor pages render faster than they would with other custom fields plugins. Each Dynamic Tag lookup is cached, so repeated access to the same field on a single page adds no additional database overhead.
For Elementor archives with Loop Grids pulling data from 20+ posts, Field Forge’s batch loading eliminates the N+1 query problem that typically slows down Elementor + ACF combinations.
If you’re currently using ACF + Elementor’s ACF integration, migration to Field Forge is straightforward:
Most Elementor templates work unchanged after migration. In some cases, you may need to reselect the Dynamic Tag source from “ACF Field” to “Field Forge Field” in individual widgets, but the underlying data is the same.
Get Field Forge — from $35/year →
Elementor integration is included in every version of Field Forge, including the free one.