40 CARROTGet your army into 40 Carrot
Import a .json, .ros, or .rosz file for free, use Full Access for pasted army-list text, or build the units by hand.
How do you make printable Warhammer 40K data cards?
Print the profiles you actually use instead of hunting through several screens at the table. The useful boundary is simple: 40 Carrot formats the information you entered; it does not replace your current rules source.
TL;DR
Build or import the army, choose Printable Data Cards, select the units, and review every profile before printing. 40 Carrot lays the cards onto print-ready sheets and handles page breaks. Pasted army-list text and tools that fill a profile from pasted text are Full Access shortcuts; printing itself is not.
Why print from the same army you use on the table?
The Data Cards panel accepts the same .json, .ros, and .rosz files as the army importer, plus supported list text for Full Access accounts. Review and fine-tune the units before arranging the sheets.
Start through the army importer when a file already carries useful data, or use the manual unit builder for a custom unit. A bundled database match provides the unit name, base size, and current official points; you enter the gameplay characteristics from your own rules source.
From army to printed sheet
Keep the profile review between import and print. A neat card with stale numbers is still a bad table reference.
Open the data card generator
Choose Printable Data Cards and select the units you want on the sheets.
Review the profiles
Check the stat line, weapon profiles, abilities, card size, and page order against the current rules source you used.
Print or export
Open Print Preview, choose a sheet layout and scale, then use the browser's print dialog. Page breaks and optional cut lines are handled for you.
Inspect the army behind the cards
This published frame shows a real imported army on the true-scale table. It demonstrates the roster context behind the cards, not the print preview; open Printable Data Cards in the app to review sheet layout, scale, and cut lines.
What appears on each card?
Each card is a table-side reference for one unit. It can show the stat line, weapon profiles, abilities, and the other details you added in the builder. Weapon names and characteristics wrap inside their own rows so adjustable card widths do not force the profile into an unreadable fixed column.
Custom and converted units work the same way. If you can build the unit profile, you can print it. That flexibility also means you own the accuracy check: compare the preview with the current book, errata, and event pack before relying on it in a game.
Pre-print check
- Profiles
- Stats, saves, wounds, OC, weapons, abilities, and model count checked against the current source.
- Sheets
- Layout, scale, card order, phase reminders, and cut lines checked in Print Preview.
- Printer
- Browser scaling set as intended and one test sheet printed before the full army.
How do you turn Data Cards into a tournament cheat sheet?
Print only the final submitted roster. Each card can carry the player-supplied stats, saves, squad information, weapons, and abilities you checked, plus short reminders that reduce phone and rule lookups without reproducing official rules text.
Useful tournament notes
- Phase
- Short Command, Movement, Shooting, Charge, Fight, and scoring reminders that tell you when to consult the current rule.
- Role
- The unit’s job, common target, important range, and the condition that changes its priority.
- Limited use
- Once-per-game abilities and conditional choices, written as cues rather than copied rules.
- Roster only
- Remove draft units and old profiles. A smaller checked set is faster to scan and harder to confuse.
These are custom player references, not official datasheets. Verify every stat, weapon, ability, save, and squad detail against the current official source and the organiser’s event pack. The pre-tournament army check helps keep the printed set aligned with the physical army.
Sheet cards or 63 by 88 mm trading cards?
The Data Cards panel carries a Card Format toggle with two settings. It describes the run you are about to print, not the tab you happen to have open, so units and Stratagems both follow it. Sheet is the setting a fresh collection opens on, and it is the format the rest of this page describes. Trading prints one merged unit, or one Stratagem, on a 63 by 88 mm card, which is standard sleeve stock.
Switching replaces nothing. Sheet cards keep their adjustable size, their two-column packing and their three layout presets, and the cards you already built are untouched either way. Both formats print on the same 8.5 by 11 inch paper through the same scale, gap and cut-line controls, and both are free.
The two formats
- Sheet
- A new collection starts at 4.7 by 2.8 inches and the size is adjustable from 2 to 12 inches. Each card packs its unit blocks into two columns, and the Portrait 1×3 sheet holds three of those cards.
- Trading
- Fixed 63 by 88 mm stock, one unit or one Stratagem per card. A portrait sheet of letter paper takes nine as a 3×3 grid, and landscape takes eight as 4×2.
- Long units
- A unit with more weapon rows than the small stock fits is scaled down so the whole block stays on the card instead of losing its last rows. That shrinking has a floor, which is why the sheet card is still there for the units that need it.
- Gap
- The trading sheet opens at a 4px gap, because three 88 mm rows use nearly the full height of the page. Widen the gap and each layout button reports the smaller count it now fits.
Sleeved cards suit a reference you pass across the table or clip to the army list. Sheet cards suit a printed page you keep beside you and read at a glance. The setting is remembered with the rest of the panel, so the next visit opens on whichever you used last.
Choose the print layout that fits your use
Print Preview shows the layouts belonging to the format you chose. Sheet cards get Portrait 1×3, Landscape 1×2, and Landscape 2×2; trading cards get Portrait and Landscape, and each button names the grid and how many cards that sheet takes. Scale and gap are adjustable, the scale control stops at the safe page limit for the current card size and gap, and cut lines are optional. The browser prints only the generated sheets, not the controls around them.
63×88trading card stock in millimetres
9trading cards on a portrait sheet
3sheet-format layouts
4.7×2.8default sheet card size in inches
Make the reference you will use
Open Printable Data Cards →Manual unit profiles, both card formats, and printing are free. Paid shortcuts can fill profiles from pasted text.
Frequently asked questions
Do I need design software to make 40K data cards?
No. 40 Carrot generates the cards from your imported or hand-built army and lays them out on print-ready sheets. You use the browser's print dialog.
Can I make cards for custom or converted units?
Yes. Any unit you create with the manual unit builder can be printed as a data card, using whatever profile and weapon stats you entered.
What size are the trading card format cards?
63 by 88 mm, which is standard sleeve stock, with one unit or one Stratagem per card. A portrait sheet of letter paper takes nine of them and landscape takes eight. Sheet cards are unchanged and keep their own adjustable size and layouts.
Which units are in the built-in database?
40 Carrot ships a built-in library of unit names, base sizes, and current official points that you can search and place directly. You enter each unit's stats yourself from your own book, then print.
Is the data card generator free?
Yes. Building and printing data cards is free with a free account: add units by hand, arrange the sheet, and print. Full Access ($4/month or $33 lifetime) adds the auto-fill shortcuts, such as army-list text import and tools that fill a card from profile text you paste.
Can I use custom Data Cards as a tournament cheat sheet?
Yes, as a player-made reference. Print only the submitted roster, keep reminders short, and verify every stat, weapon, ability, save, and squad detail against current official sources. The cards are not official datasheets.