Using Adobe XD Repeat Grid to Speed Up List‑Heavy Designs

The problem: duplicated cards become a maintenance burden

When a screen needs many similar rows — settings, product cards, team members — designers often copy‑paste a single card dozens of times. Any later change to spacing, corner radius, or typography forces you to edit each copy individually, which is error‑prone and slows down iteration.

How Repeat Grid works in Adobe XD

Select an element or a small group (for example, an avatar shape plus two text layers). Hover over the bottom or right edge of the selection until the cursor changes to a double‑arrow repeat‑grid handle. Drag outward to create rows and columns; XD tiles the selection into a grid. The grid has two editing modes:

• Master edits: change the size, fill, corner radius, or gutter spacing of the original element; those changes propagate to every cell while preserving any per‑instance overrides.
• Instance overrides: double‑click a text layer or image placeholder inside a specific cell to edit its content; that edit stays local to that cell and does not affect the master.

You can also seed the grid with data: copy a column of text from a spreadsheet or plain‑text file, select a text layer inside the grid, and paste. XD distributes the values across instances in order. The same technique works for image shapes — paste a list of file names or drag a folder of photos onto an image placeholder and XD fills them sequentially.

Worked example: building a 3×4 team grid

1. Draw a simple card: a circle (avatar), a text layer for the name, and a text layer for the role. Group these three objects.
2. With the group selected, hover the bottom edge until the repeat‑grid cursor appears, then drag down to create three rows and right to create four columns (a 3×4 grid).
3. Copy a column of twelve names from your spreadsheet (e.g., [Your Spreadsheet Column]) and a column of twelve roles. Select the name text layer in the top‑left cell, paste the names; XD fills the name fields row‑by‑row. Repeat for the role layer.
4. Drag twelve avatar photos (or a folder) onto the first circle placeholder; XD distributes them across the twelve instances.
5. To adjust the overall look, select the master card (any cell, then press Esc to exit isolate mode) and increase the corner radius from 8 px to 12 px. Observe that every avatar’s corners update instantly while the names and roles you edited remain unchanged.
6. Finally, adjust the gutter spacing by dragging the horizontal or vertical repeat‑grid handle; the space between all cards changes uniformly.

You can verify the behavior at any time:

• Edit a single cell’s name and confirm that only that cell changes.
• Change the master’s fill color and confirm the update appears across all cells.
• Modify the gutter and watch the spacing update globally.

Trade‑offs and limitations

Repeat Grid is a layout convenience, not a data‑driven component system. It does not generate code, bind to real data, or expose overrides as props. Consequently:

• No nesting: you cannot place a Repeat Grid inside another Repeat Grid. If you need a two‑level list (e.g., sections each containing a grid), you must duplicate the outer grid or use separate components.
• Maintenance overhead with many overrides: when most cells have unique text or images, the grid becomes harder to reason about because the master‑detail relationship is weakened. In such cases, creating a few hand‑built variants or using a component with states may scale better.
• Frozen feature: Adobe has placed XD in maintenance mode; Repeat Grid will not receive new enhancements. Teams should retain export paths (SVG/PNG, .xd files) and consider migration strategies if they plan to move to another design tool.

Practical closing advice

Use Repeat Grid when you need a quick, editable mock‑up of a repeating visual pattern and you anticipate only a few global style tweaks. Keep the master lean, limit per‑instance overrides to content that truly varies, and treat the grid as a specification rather than a production‑ready component. When the design stabilizes, consider converting the master into a reusable component with states for interactive work, and archive the Repeat Grid file as part of your design‑system documentation.