This section answers the questions that come up most often from content managers and site administrators using Field Forge. If your question is not here, check the Troubleshooting section below for technical issues, or visit the Field Forge documentation site for more specialized guides.
What is the difference between Field Forge and ACF Pro?
Both plugins add custom fields to WordPress posts and pages, and they use the same template functions in your theme code (get_field(), the_field(), have_rows()). The core differences are architectural and feature-based. Field Forge stores data in optimized custom database tables instead of the wp_postmeta table, resulting in significantly fewer database queries on sites with many fields. It also includes features ACF does not offer: AI-powered field generation from natural language descriptions, built-in revision history with visual diffs and one-click rollback, and TypeScript/GraphQL export for modern development workflows. The migration tool lets you switch from ACF to Field Forge without changing your theme code.
How many field groups can I create?
On the free plan, you can create up to 3 field groups. Each group can contain as many individual fields as you need — the limit is on groups, not fields. On the PRO plan, there is no limit on field groups.
Will my theme break if I switch from ACF?
No. Field Forge provides all ACF-compatible functions: get_field(), the_field(), have_rows(), get_sub_field(), the_sub_field(), and all others. Any theme code that worked with ACF works identically with Field Forge. The migration tool handles both field group definitions and data. Your theme does not know or care which plugin is providing the functions.
Do I need to know code to use Field Forge?
Not for daily use. Content managers create field groups using the visual editor (point-and-click, no code) and fill in fields on posts using the familiar WordPress editing screen. A developer is needed for two things: (1) adding template code that displays field data on the frontend of your website, and (2) creating advanced configurations like custom post types or complex Flexible Content layouts that match your site’s design system.
Can I use Field Forge alongside Elementor, Divi, or other page builders?
Yes. Field Forge handles structured data (product specifications, team member profiles, pricing tables), while page builders handle visual layout design. Many professional sites use both — the page builder for general page design and Field Forge for structured, queryable content that needs to be consistent across the site. If your page builder needs to read Field Forge data for dynamic content, enable “Sync to PostMeta” in settings.
What happens if I deactivate Field Forge?
Your data remains safely in the database. If you reactivate Field Forge later, everything comes back exactly as you left it. While the plugin is deactivated, the custom fields will not appear in the editor and the data will not be available on the frontend (unless your theme has its own fallback logic). Deactivating does not delete any data.
Can I use Field Forge on a multisite network?
Yes. Field Forge can be network-activated (applies to all sites in the network) or activated on individual sites. Each site in the network has its own independent field groups and data. PRO licenses support multisite — check your plan tier for the number of allowed site activations.
How do I display field data on my website?
Field Forge stores the data; your theme controls how it appears to visitors. Your developer adds template code using functions like get_field('hero_title') to retrieve the data and render it in HTML. If you can see fields and enter data in the WordPress editor but nothing appears on the website, it means the theme template has not been updated to display those specific fields. Contact your developer to add the necessary template code.
Can I duplicate a field group?
Yes. On the Field Groups list page, hover over any field group and click Duplicate. This creates an exact copy with “(Copy)” appended to the title. You can then rename it and modify the fields as needed. This is useful when you want a similar field structure for a different post type.
What happens to my data if I upgrade from Free to PRO?
Nothing changes with your existing data. The upgrade simply unlocks additional features (Repeater, Flexible Content, Groups, Options Pages, AI generation, export/import) and removes the 3-field-group limit. Your existing field groups and all the content data your editors entered remain exactly as they are.
Can I use conditional logic to show or hide fields?
Yes. Each top-level field in a group can carry a Conditional Logic rule set that controls whether the field shows on the post edit screen. Open a field’s settings in the field group editor, tick Conditional Logic, and add rules of the form Field — operator — Value. Multiple rules in the same group are joined with AND; click + OR group to add an alternative path. The runtime evaluator updates visibility live as the editor changes a trigger field, and the initial render also pre-hides fields whose rules are false so there is no flash of all-fields on page load.
Available operators: equals, not equal to, contains, does not contain, matches pattern (regex), is empty, is not empty, and the four numeric comparisons (>, =, <=). Hidden trigger short-circuit is built in — if a trigger field is itself hidden by another rule, conditions on it count as false, so chains (A controls B controls C) cascade correctly. Hidden fields keep their stored values; if a tester re-shows the field later, the previous value is still there.
Conditional logic on sub-fields inside Repeater / Group / Flexible Content is not yet evaluated at runtime — those rules round-trip through import/export but every sub-field still renders. Use top-level Conditional Logic for now, or stay on ACF Pro for nested-conditional cases.
Is Field Forge compatible with my hosting provider?
Field Forge works on any standard WordPress hosting that meets the minimum requirements: PHP 7.4+, MySQL 5.6+ (or MariaDB 10.1+), and WordPress 5.8+. This includes shared hosting (Bluehost, SiteGround, HostGator), managed WordPress hosting (WP Engine, Kinsta, Flywheel), and VPS/dedicated servers. No special server configuration is needed.
How do I get support if something goes wrong?
PRO users can submit support tickets through the license management dashboard on the Field Forge website. Include your WordPress version, Field Forge version, PHP version, a description of the problem, and any relevant screenshots. Free plan users can access community forums and the documentation site for self-service help.
> Good to know: If you have a question not covered in this section or the Troubleshooting section below, visit the Field Forge documentation site for detailed guides, video tutorials, and searchable help articles. You can also contact support through the PRO license dashboard.
—