A testimonials section with 8 entries, a team page with 12 profiles, a pricing table with 4 plans — all the same layout, repeated with different data. Building each one as a separate set of blocks means any layout change has to be repeated by hand across every item. Nexter’s Repeater Block, introduced alongside Glassmorphism in June 2025, pulls the data from ACF, SCF, or JetEngine and repeats one layout across it automatically — and knowing which of those three data sources fits your project, plus how to keep a large repeater fast, matters as much as the block setup itself.
What the Repeater Block Actually Does
Instead of manually placing and styling each testimonial, team member, or FAQ item as its own set of blocks, you define the layout once and point it at a repeater field from a custom-fields plugin. The block then renders one instance of that layout per entry in the field — add a new team member to the underlying data, and a new card appears automatically, styled exactly like the rest.
ACF vs. SCF vs. JetEngine: Which Data Source to Actually Use
The three plugins named in this block’s data-source options aren’t interchangeable in the way they might first appear, and the split between two of them is recent enough to be worth explaining. Advanced Custom Fields (ACF) is the long-running commercial plugin, owned by WP Engine since 2022; its Repeater field type is a Pro-only feature. Secure Custom Fields (SCF) is a separate, free plugin that WordPress.org’s security team forked from ACF in October 2024, during the public dispute between WordPress.org and WP Engine — SCF carries the same repeater-field capability ACF Pro does, but at no cost, since it was forked before the Pro/free split existed as a licensing boundary. JetEngine is a fully independent plugin with its own repeater-equivalent (Meta Box/glossary and listing tools) built around a different underlying data model entirely. For a new project with no existing field data, SCF’s free repeater field type is the lowest-cost entry point into this block; for a site that already has ACF Pro field groups built out, sticking with ACF avoids a migration; JetEngine tends to fit best on sites already using its broader listing/query-builder ecosystem for other dynamic content.
Setting Up a Repeater Field
- Make sure Nexter Blocks Pro is active, and toggle on the Repeater block under Nexter Blocks → Blocks.
- In ACF Pro, SCF, or JetEngine, create a repeater field — for example, “Steps List” with subfields like Step Title (text), Description (textarea), and Step Image (image).
- Assign the field group to the post type you’ll use (posts, pages, or a custom post type).
- Edit an actual post or page and fill in sample entries in the repeater field.
Connecting the Block to Your Data
Add the Repeater block to the page where you want the section to display. From the Source dropdown, pick the post type your field is assigned to, select the repeater field itself, then choose the specific post holding the data you want to pull in. From there, choose a pre-made listing layout or build a custom one from Nexter’s own blocks, and fine-tune columns and spacing from the Extra Options tab.
Also Read: Nexter Blocks AI Features: What the New AI-in-Every-Block Update Actually Does — AI generation now works inside repeater fields too, for testimonials, team listings, and more.
Why a Large Repeater Can Quietly Slow a Page Down
This is the part of using a repeater field that isn’t obvious until a site has grown: every subfield in every row of a repeater is its own row in WordPress’s wp_postmeta table under the hood. A repeater with 200 rows and 5 subfields each is over 1,000 meta rows for that single post, and without a persistent object cache, every page load that touches that field can issue that many database reads. Image subfields specifically make this worse when set to return a full image array or URL rather than just an ID — each one can trigger its own additional query, so a repeater with 10 rows each containing an image can add 10 extra queries beyond the base repeater read. None of this is a Nexter-specific problem; it’s inherent to how repeater fields store data in WordPress, and it applies the same way whether the underlying source is ACF, SCF, or a comparable plugin.
The practical fixes, in order of effort: set image subfields to return an Image ID rather than a full array or URL (the lightest-weight option); enable a persistent object cache on the site if one isn’t already running, which caches repeated reads of the same field data across page loads; and for a genuinely large dataset (hundreds of entries), consider whether the content actually belongs in a custom post type with its own query instead of a single post’s repeater field, since repeaters are built for a moderate number of structured rows, not a full catalog-sized dataset.
A Worked Example: A 15-Person Team Page
Take a real case: an agency site needs a team page for 15 people, each with a headshot, name, title, and a two-sentence bio. Built by hand as separate blocks, that’s 15 nearly-identical card layouts, each needing its own manual updates if the design changes later — add a LinkedIn icon to every card, and it’s 15 separate edits. Built with the Repeater block instead: create a repeater field called “Team Members” with subfields Name (text), Title (text), Bio (textarea), Headshot (image), and LinkedIn URL (URL), assign it to a page, fill in the 15 entries, then build the card layout once in the Repeater block and connect it to that field. Adding the LinkedIn icon later means editing the one layout definition, and it appears on all 15 cards immediately. Because there are only 15 rows with 5 lightweight subfields each (about 75 meta rows total), this size comfortably sits well below the range where repeater performance actually becomes a concern — the object-cache and image-ID advice from above matters more once a listing grows into the hundreds of rows, not at this scale.
Troubleshooting Common Repeater Issues
- The block shows no entries even though the field has data: double check the Source dropdown is pointing at the correct post type, field, and specific post — a mismatch anywhere in that three-step chain is the most common reason a repeater renders empty.
- New entries added to the field don’t appear on the page: confirm any page or object caching has been cleared; a repeater pulling from a cached page won’t reflect a just-added row until the cache updates.
- Images in the repeater load slowly on a page with many rows: check the image subfield’s return-value setting — a full image array or URL return type can add one query per image, where an Image ID return type avoids that overhead.
- The layout looks fine with sample data but breaks with real content: test with a genuinely long bio or an unusually long name in at least one entry before launch; layouts built and eyeballed against short placeholder text often don’t account for real-world content length variance.
What You Can Build With It
- FAQ sections — add new questions and answers without duplicating markup
- Service or feature grids, each with an icon, title, and description
- Testimonial walls of any length
- Pricing plan sections
- Team member listings with uniform profile cards
One caution worth flagging specifically for the FAQ use case: if the repeater-driven FAQ section is meant to also earn FAQ rich results in search, that requires separate FAQPage schema markup handled correctly (and, on Nexter specifically, that schema is often best left to a dedicated SEO tool rather than hand-authored, to avoid a duplicate-schema defect if something else on the page already emits it) — the Repeater block itself only handles the visible layout, not structured data.
To learn the full field-mapping process in depth, Nexter’s own documentation covers it step by step: How to Display Dynamic Repeater Field Data in WordPress.
FAQ
Do I need ACF Pro specifically, or does the free version work?
Repeater fields are an ACF Pro feature (the free ACF plugin doesn’t include the Repeater field type); SCF and JetEngine offer their own repeater-field equivalents that also work with this block.
Is the Repeater block available on Nexter Blocks free?
No, the Repeater block is a Nexter Blocks Pro feature.
Can I use a pre-made layout instead of designing one from scratch?
Yes. After connecting your data source, you can pick a pre-made visual+text layout or build a fully custom one using Nexter’s other blocks.
What’s the actual difference between ACF and SCF?
SCF is a free plugin WordPress.org forked from ACF in October 2024 during a dispute with ACF’s owner, WP Engine. SCF includes the Repeater field type at no cost, since it was forked before ACF’s Pro/free licensing split applied to it; ACF itself remains a separately developed commercial plugin where the Repeater field requires ACF Pro.
How many rows can a repeater field handle before it slows the page down?
There’s no fixed number, but a few hundred rows with multiple subfields each is where real performance impact typically starts, especially without a persistent object cache. Setting image subfields to return an ID rather than a full array, and considering a custom post type for genuinely large datasets, are the standard mitigations.
Why does my repeater section show no entries even though I filled in the data?
The most common cause is a mismatch in the block’s Source settings — the post type, the specific field, and the specific post all have to line up correctly. Re-check each of those three selections before assuming the field data itself is the problem.
At what point should I move data out of a repeater field into a custom post type instead?
There’s no hard cutoff, but once a listing grows toward hundreds of entries rather than dozens, a custom post type with its own query typically performs and scales better than a single post’s repeater field, which is built for a moderate, structured set of rows rather than a full catalog.
Conclusion
None of this requires custom code, but it does require a repeater field already set up in ACF, SCF, or JetEngine — that’s the one prerequisite most builders forget to check before reaching for this block. Get that piece right first, pick the data source that fits your project (SCF for a fresh free start, ACF if you already have field groups, JetEngine if you’re already in its ecosystem), keep an eye on row count and image-field return type as the dataset grows, and the block itself is a five-minute connection.
Suggested Reading
- Nexter Blocks AI Features: What the New AI-in-Every-Block Update Actually Does
- Nexter Blocks Countdown, Progress Bar and Infobox: Building a High-Converting Landing Page Section
- Nexter Blocks Global Border and Block Presets: Speeding Up Your Design Workflow
