--- title: "Nexter Fields vs ACF, Meta Box and Pods" url: https://nexterwp.com/docs/nexter-fields-vs-acf-metabox-pods/ date: 2026-11-12 modified: 2026-11-12 lang: en author: "Aditya Sharma" description: "If you already use a custom fields plugin, the question is whether moving is worth it. This page is a straight comparison, including what Content Fields does not do. What..." image: https://nexterwp.com/wp-content/uploads/2026/09/nexter-fields-vs-acf-metabox-pods-1024x519.jpg word_count: 394 --- # Nexter Fields vs ACF, Meta Box and Pods ## Key Takeaways - Content Fields ships 22 selectable field types on Nexter Extension, or 24 with Nexter Pro Extensions, and it also includes custom post types, taxonomies, and an import path in one plugin rather than two. - Migration supports ACF, Secure Custom Fields, Meta Box, and Pods, but JetEngine is not currently supported, and the source plugin stays untouched so data copies can be verified before switching anything off. - Nexter Blocks uses field values as dynamic content, but Elementor is not supported in 4.9.0, and the template API is not a drop-in replacement because get_field() calls must be rewritten. If you already use a custom fields plugin, the question is whether moving is worth it. This page is a straight comparison, including what Content Fields does not do. ## What It Does Content Fields covers the ground most sites need — 22 field types on Nexter Extension (24 with Nexter Pro Extensions), custom post types, taxonomies and an import path — inside Nexter Extension, so it is one plugin rather than two. ## Before You Start - You currently use ACF, Secure Custom Fields, Meta Box or Pods.- You have a site you can back up and test on. ## What to Weigh Up - **Field types.** Content Fields ships 22 selectable types on Nexter Extension, and 24 with Nexter Pro Extensions — *Relationship* and *Repeater* are Pro — covering the common ground. ACF has more, especially at the layout end. - **Post types and taxonomies.** Built in, so you do not need a second plugin for them. - **Migration.** Importers exist for ACF, Secure Custom Fields, Meta Box and Pods. JetEngine is not currently supported. ![The Import Data button, where a migration starts](https://nexterwp.com/wp-content/uploads/2026/09/nxt-fields-s-import-data-button.webp) - **Template code.** This is the real cost of moving — see the limitation below. - **Page builders.** Field values work as dynamic content in Nexter Blocks. Elementor is not supported. - **Machine access.** Content Fields exposes WordPress abilities for AI and MCP clients. No competitor currently does. ## Limitations - **The template API is not a drop-in replacement.** There is no `nxt_get_field()` or `nxt_have_rows()`. Every `get_field()` call in your theme has to be rewritten. On a site with a lot of template code, that is the largest part of the move.- **No Elementor integration.** Field values are not available as Elementor dynamic tags in 4.9.0. If your site is built in Elementor and reads fields that way, this is a blocker.- **No WordPress core Block Bindings support** in 4.9.0, so field values cannot be bound to core blocks that way.- ACF has a deeper feature set at the edges — flexible content, clone fields and a larger ecosystem of add-ons. ## Troubleshooting ### Can I run Content Fields alongside my current plugin? Yes. Migration copies data rather than moving it, and the source plugin is left untouched, so you can verify before switching anything off. ### Will my existing template code keep working? Only while the old plugin is still active. Nexter does not provide identically named functions, so plan the rewrite as part of the migration. ## Related Docs - [Migration overview](https://nexterwp.com/docs/migrate-custom-fields-to-nexter/)- [Migrate from ACF](https://nexterwp.com/docs/migrate-acf-to-nexter-fields/)- [Template functions reference](https://nexterwp.com/docs/nexter-fields-template-functions/) ## Frequently Asked Questions **Q: What is the best ACF alternative for WordPress custom fields?** A: Nexter Fields is the closest fit if you want custom fields inside one plugin instead of splitting the job across separate tools. It covers 22 field types on Nexter Extension, 24 with Nexter Pro Extensions, plus custom post types, taxonomies, and an import path. The tradeoff is that ACF still goes deeper at the edges, especially with flexible content, clone fields, and a larger add-on ecosystem. **Q: Is there an ACF repeater alternative in Nexter Fields?** A: Repeater is available, but it sits in the Pro side of the stack. Nexter Fields ships 22 selectable types on Nexter Extension and 24 with Nexter Pro Extensions, and Relationship plus Repeater are part of that Pro set. That makes it a practical ACF repeater alternative for sites already planning to use the broader Nexter setup, not just a single field type. **Q: Can I switch from ACF to Nexter Fields without breaking my site?** A: The migration path is built around copying data, not ripping out the old setup. Importers exist for ACF, Secure Custom Fields, Meta Box, and Pods, while JetEngine is not currently supported. The safest move is to back up first and test on a site copy so you can confirm the imported data before turning anything off. **Q: Will my existing ACF template code keep working after migration?** A: Only while ACF stays active. Nexter does not provide identically named functions like nxt_get_field() or nxt_have_rows(), so every get_field() call in your theme has to be rewritten. That rewrite is usually the real cost of moving, especially on sites with a lot of template code. The [Template functions reference](https://nexterwp.com/docs/nexter-fields-template-functions/) is the key piece for planning that change. **Q: Does Nexter Fields work with Elementor dynamic tags?** A: No Elementor integration is a hard limitation in 4.9.0. Field values are available as dynamic content in Nexter Blocks, but they are not available as Elementor dynamic tags in that version. If your current site depends on Elementor reading custom fields directly, that becomes a blocker rather than a minor inconvenience. **Q: Should I move from Meta Box or Pods to Nexter Fields?** A: The move makes sense when you want custom fields, post types, and taxonomies inside one plugin and you are okay rewriting template code. Nexter Fields also exposes WordPress abilities for AI and MCP clients, which none of the competitors do on this page. If your site leans heavily on advanced edge features or Elementor-based field output, the switch is harder to justify.