Adobe XD Repeat Grid: When One Managed Grid Beats Forty Pasted Layers
Repeat Grid turns copy-paste drudgery into a managed pattern: layout edits propagate everywhere, content stays per-cell, and spacing is one drag. Here's a worked example and where the trade-off bites.
25 Feb 2026, 21:25 UTC

You've designed a product card. Now the mockup needs twelve of them, each with a different photo, title, and price. The old workflow — copy, paste, nudge, repeat — leaves you with forty loose layers and a spacing change that takes twenty minutes. Repeat Grid exists to kill that workflow: you design the cell once, and XD manages the duplicates as a single entity.
The thesis here is simple: Repeat Grid is the right default for any repeated, uniform UI pattern (lists, galleries, pricing tables), but it trades per-element flexibility for layout consistency. Knowing where that trade-off bites is what makes it useful instead of frustrating.
What Repeat Grid actually manages for you
Select any group of elements — say an image, a title, and a price label — and press Cmd/Ctrl + R (or click Repeat Grid in the Properties panel). XD wraps the selection in a grid container with green drag handles on the right and bottom edges. Dragging a handle adds or removes rows and columns; the cells in between are generated, not pasted.
Three behaviors follow from that managed structure:
- Layout edits propagate. Change the corner radius, font size, or padding inside one cell and every cell updates. You edit the pattern, not the instances.
- Content stays independent. Text and images can differ per cell even though the layout is shared. You can drag a batch of images from Finder/Explorer straight onto the grid and XD distributes one per cell, or paste a multi-line text block to fill titles in order.
- Spacing is a single value. Hover the gap between cells and drag to adjust row or column gutters globally, instead of re-aligning dozens of layers.
The practical payoff is a file with one grid object instead of 48 layers, and a layout experiment — "what does this look like at 3 columns instead of 4?" — that takes a drag, not an afternoon.
A worked example: a product listing card
A concrete pass through the feature, assuming a current desktop build of XD:
- Draw a 260×320 rectangle for the card background. Add an image placeholder at the top, a title text layer, and a price text layer. Group them (
Cmd/Ctrl + G) and name the group something meaningful, likeproduct-card. - With the group selected, press
Cmd/Ctrl + R. Green handles appear on the group's right and bottom edges. - Drag the right handle to create three columns, the bottom handle for two rows. You now have six cells.
- Select six product photos in your file manager and drag them onto the grid. Each cell gets a different image. Then copy six lines of product names from a text file, select the title layer in one cell, and paste — XD fills the titles down the grid.
- Hover the gap between two cells until the pink spacing guides appear, then drag to set a 24px gutter. All gaps update together.
To verify it behaved as expected: edit the price label's color in one cell and confirm every cell changes; then change one cell's title text and confirm the others do not. That pair of checks — layout propagates, content doesn't — is the whole mental model.
Where the trade-off shows up
Repeat Grid assumes uniformity, and that assumption has teeth:
- Ungrouping is destructive. If you need one cell to animate differently or break the pattern, you ungroup the grid back into individual layers — and there's no way to re-constitute it as the same managed grid. Do per-cell animation work on a duplicated artboard, not your source layout.
- It fakes responsiveness. A grid with fixed cell sizes tells you nothing about how the list behaves at 360px wide. Treat grid output as a visual draft, and validate real wrapping behavior in a prototype or in code.
- Irregular layouts fight it. A featured-first-item pattern or a masonry gallery will have you ungrouping within the hour. If more than one or two cells need to deviate, components with overrides are usually the better tool.
One more caveat worth stating plainly: Adobe XD is in maintenance mode — Adobe ended active feature development after the Figma acquisition attempt, and no new capabilities are shipping. Repeat Grid itself is stable, well-documented behavior, but factor the product's status into any decision to start new design-system work in XD.
The actionable part
Next time you catch yourself about to paste a third copy of anything in XD, stop and press Cmd/Ctrl + R instead. Build the cell, drag the handles, batch-drop the content, and keep the grid intact as long as the layout is uniform. The moment two or more cells need to diverge, duplicate the artboard, ungroup there, and let the grid keep doing the job it's good at: making the boring 90% of repeated UI nearly free.
0 replies
A thoughtful contribution can make all the difference. Be the first to share one.