A repeater repeats one design for every item in a collection. It is how a blog list, a product grid, or a team page stays in sync with the CMS.
Last updated
You design one row. Remake fills it with as many rows as there are items.
Add a Repeater block, then open the Repeater tab and choose a collection.
Inside the repeater is one item template. Put the layout and content for a single item there. Use variables to pull in the item's fields.
For example, a blog card might contain:
An image bound to the cover field.
A heading bound to the title.
A paragraph bound to the excerpt.
A link to the item page.
Type $ inside the repeater to open the variable picker. Choose the field you want. The variable shows the current item's value when the page renders.
Read Variables and conditions for formatting and date options.
Use the Columns setting to show the items in a grid. Choose 1–12 columns.
The column count follows the device selected in the toolbar. Set 3 on Desktop, 2 on Tablet, and 1 on Mobile portrait to get a responsive grid without writing classes.
Filters narrow the list. You can match all conditions or any condition.
Each filter compares a field to a value, for example:
Category equals "News".
Price is greater than 20.
Featured exists.
Title contains "guide".
Filters are useful for showing a subset without creating a separate collection.
Sort by one or more fields, ascending or descending. The default is newest published first.
A common setup is:
Featured items first.
Then published date, newest first.
Set a limit when you want a short list, such as the three latest posts on the home page.
Leave the limit high enough when you add pagination. The page size and the limit work together.
A single repeater can load up to 200 items per render. For longer collections, use pagination instead of raising the limit.
Turn on Paginate items and add a pagination block. You can show:
Page numbers.
Previous and next links.
Numbers with previous and next.
A full control with first and last.
Pagination is better than an endless list for content people want to browse in order.
A repeater can read search values from the URL. This lets a normal form filter a list without custom code.
Add a form with the action Search collection list.
Choose the collection's list page as the results page.
Give the form fields clear input names, such as q for text or category for a dropdown.
In the repeater's Search settings, map those names to the fields they should search.
When the form is submitted, the page reloads with the values in the address, and the repeater shows only matching items.
Empty search values are ignored, so an untouched form shows everything.
Turn on the item link to send each row to its item page. This requires the collection to have pages.
The link uses the item's slug, so each row points at its own page automatically.
A nested loop repeats a related set of items inside the main row. Use it when a field is a relation to another collection.
For example, a post can show its author, and a category page can show its posts. The nested loop is an advanced feature; start with a simple repeater and add nesting when the content needs it.
Repeaters show published items only. Drafts and scheduled items stay hidden until their publishing time.
If a list looks empty, check the item status first.
For a home page with the latest posts:
Add a repeater and choose the Posts collection.
Design one card.
Bind the cover, title, and excerpt.
Sort by published date, newest first.
Set the limit to 3.
Turn on the item link.
Add a button below the repeater that links to the full blog list.
Then publish the page. New posts appear automatically when they are published.
A website builder that works like a document. CMS, forms and EU hosting included.
© 2026 Remake. All rights reserved.
