TLDR
For customer-supplied artwork, build each card at its final 2.5 × 3.5-inch trim size, add 0.125 inch of bleed on every edge, keep critical text and symbols at least 0.125 inch inside the trim line, and use images with at least 300 dpi of effective resolution. Export at 100% scale, preferably as a print-ready PDF or PDF/X file, with CMYK color and embedded or outlined fonts. Then proof the card content, front/back pairing, quantities, versions, and filenames yourself; a printer’s technical preflight is not a substitute for checking the deck.
First decide whether you need files or a decklist
“Print-ready” means different things for an existing Magic printing and an original custom card. Do not spend an evening manufacturing image files if the ordering workflow can already find the cards from a clean decklist.
| Project type | Best starting point | Main review task |
|---|---|---|
| Existing Magic printings | Quantity-first decklist | Select the intended set, art, frame, and treatment |
| Original custom cards | Individual artwork files or a print-ready PDF | Check dimensions, bleed, safe area, resolution, fonts, and color |
| Mixed deck | Decklist plus a separate custom-card batch | Reconcile quantities and keep the two workflows clearly labeled |
| Double-faced or paired cards | Manifest with explicit front/back relationships | Verify orientation and prevent mismatched faces |
PrintMTG says its decklist importer accepts lists from Moxfield, Archidekt, MTG Arena, and plain text. Its preferred plain-text structure is one card per line with the quantity first, such as “2 Brainstorm” or “2x Brainstorm.” Versions can then be reviewed after import. Inline notes, spreadsheet columns, and extra descriptors can produce warnings or failed matches. Review the supported decklist formats and common import errors
If your project is made from existing printings, a physical MTG playtest-card printing workflow can therefore be more reliable than assembling a folder of images manually. For a Moxfield-specific process, use the decklist cleanup, version review, and archiving workflow. Custom artwork still needs a proper file-preparation pass.
Use the finished card size, then add bleed
PrintMTG’s current customer-file requirements list a finished card size of 2.5 × 3.5 inches, approximately 63 × 88 mm. For artwork that runs to the edge, the specification calls for 0.125 inch, or about 3 mm, of bleed on all four sides. That creates an overall canvas of approximately 2.75 × 3.75 inches, or 69.9 × 95.3 mm. See the current print-file requirements
| File element | Physical size | Pixels at 300 dpi | Purpose |
|---|---|---|---|
| Finished trim | 2.5 × 3.5 in | 750 × 1,050 px | Final card after cutting |
| Canvas with bleed | 2.75 × 3.75 in | 825 × 1,125 px | Allows artwork to extend beyond the cut |
| Minimum safe inset | 0.125 in inside trim | About 38 px at 300 dpi | Protects text, mana symbols, and other critical details |
The pixel dimensions above are calculations based on the stated physical dimensions and 300 dpi requirement. They are minimum planning numbers, not a reason to resample a tiny image upward. Changing an image’s resolution label from 72 to 300 dpi does not create missing detail. Check the effective resolution at the final placed size.
PrintMTG requests at least 300 dpi for images and artwork at final size. It recommends 600–1200 dpi for bitmap or line art, where sharp edges are especially sensitive to rasterization. At 600 dpi, a 2.75 × 3.75-inch canvas would be 1,650 × 2,250 pixels.
Bleed and safe area solve different problems
Bleed protects the edge. Extend backgrounds, borderless illustrations, textures, and frames through the entire bleed area so a small cutting shift does not expose an unintended white sliver.
The safe area protects information. Keep rules text, names, mana costs, power and toughness, collector details, and other important elements at least 0.125 inch inside the trim line. Bleed does not make an edge-hugging title or text box safe. For a closer visual review process, see the guide to bleed and edge-crop risks on borderless cards.
Inspect every full-art design at high zoom and at actual printed size. High zoom reveals clipping and image seams; actual size reveals whether the text is realistically readable. A file can look gloriously detailed across a large monitor while turning into ant-sized rules text on a physical card.
Organize an image batch like a reproducible deck project
A folder containing 100 attractive JPGs is not yet a dependable 100-card project. You also need a manifest that says what each file represents, how many copies to print, and which files belong together.
Retain three project states: the untouched source export, a cleaned print list, and the final approved configuration. For version-sensitive cards, record set codes and collector numbers instead of relying on descriptions such as “the dark one” or “the borderless art.” Those identifiers make a later replacement or reprint much easier to reconstruct.
Use filenames that survive sorting and reorders
Give every supplied file a descriptive, versioned name. A practical pattern is quantity-card-name-set-collector-face-version. For example, “01-card-name-SET-123-front-v2.pdf” communicates far more than “final-new-3.pdf.” Avoid using “final” until the file has actually passed the final proof.
- Keep one manifest row for every printable face or file.
- Record quantity separately instead of duplicating files without explanation.
- Use consistent “front” and “back” labels for paired faces.
- Separate tokens and helper cards from the playable-deck count.
- Record the approval date and revision number for the completed batch.
- Archive the exported PDF, manifest, and source files together.
Review special cards individually
Modal double-faced cards, transform cards, meld components, split cards, Adventures, and Battles deserve individual review. Keep paired fronts and backs adjacent in the manifest, and verify that both faces use the same revision. Track tokens, emblems, copy tokens, and helper cards as extras rather than quietly mixing them into the main-deck total.
This is also where you catch a surprisingly common batch failure: the card count is technically correct, but one back face belongs to an earlier design revision. Quantities alone cannot detect that problem.
Export a PDF without changing the scale
For supplied custom artwork, PrintMTG identifies print-ready PDF as its preferred format and says PDF/X is preferred. It requests CMYK color rather than RGB, plus embedded or outlined fonts; outlining is preferred where feasible. Native-file submissions should include the document, linked images, fonts, and a reference PDF.
- Set the document to the full bleed dimensions, not merely the finished trim size.
- Confirm that artwork reaches every bleed edge where an edge-to-edge result is intended.
- Keep critical elements inside the safe area.
- Place images at their final dimensions and check effective resolution.
- Convert to the requested color space while watching dark artwork and saturated colors for visible shifts.
- Embed or outline fonts so substitutions cannot change line breaks or symbols.
- Export at 100% scale with no “fit to page,” shrink, or enlargement option.
- Open the exported PDF and inspect it independently from the design application.
Do not assume that a successful export preserved everything. Check the PDF page dimensions, font rendering, transparency, thin lines, black text, gradients, and front/back order. PrintMTG specifically advises a 100%-scale test print or a high-zoom PDF review before submission.
Separate technical preflight from deck proofing
A production preflight answers questions such as: Can the file be processed? Is the page size workable? Is bleed present? Are fonts and links usable? Is the resolution plausible? Can the color be printed? PrintMTG says its preflight covers those kinds of technical checks.
It does not guarantee correct rules text, spelling, quantities, art selection, rights clearance, or front/back matching. Those remain project-level checks. PrintMTG’s reprint policy likewise identifies low-resolution customer images, misspellings, incorrect uploaded art, and incorrect submitted lists as examples generally not covered as provider-caused errors.
That makes the final approved manifest important. Compare the proof against the manifest, not against memory. For a large deck, Cube, or group batch, use a second pass that checks only card identity and quantity; trying to judge typography, color, versions, and counts simultaneously makes omissions easier to miss.
Keep the intended use clear
These files are for clearly non-authentic casual and personal playtest projects, not for representing cards as authentic originals. Wizards states that sanctioned events generally require authentic Magic cards, apart from limited judge-issued proxies when a card is damaged during an event. Its policy separately discusses openly non-authentic personal playtest cards and counterfeit cards intended to deceive. Read Wizards’ proxy policy and communication
Before taking a playtest deck to a store, league, or event, check the organizer’s rules. A technically perfect PDF does not change the event’s card policy.
Frequently asked questions
Is 300 dpi enough for an MTG card file?
It is the stated minimum for images and artwork at final size in the cited requirements. Use the effective resolution after placement, not merely the number shown in the file metadata. Line art may benefit from 600–1200 dpi.
Should every card be a separate PDF?
Not necessarily. Follow the receiving workflow’s current submission instructions. Whether you supply separate files or a combined PDF, maintain a separate manifest connecting filenames, card identities, quantities, and paired faces. That document is what makes the batch auditable.
Can I submit RGB images?
The cited PrintMTG requirements request CMYK. Converting at the end can shift bright colors and deepen shadows, so review the converted export rather than assuming it will match the RGB display.
Do I need image files for cards already in Magic?
Often, no. A supported decklist importer can be the cleaner route for existing printings because it lets you match card names, set quantities, and choose available versions after import. Custom artwork and original designs require a separate file workflow.
Final preflight before submission
- Confirm 2.5 × 3.5-inch trim dimensions and the required bleed canvas.
- Check at least 300 dpi of effective resolution at final size.
- Extend edge artwork through the bleed and protect critical details with the safe area.
- Verify CMYK conversion and inspect dark or highly saturated art.
- Embed or outline fonts.
- Export at 100% scale without fit-to-page processing.
- Compare every file, face, quantity, token, and helper card against the manifest.
- Review set codes and collector numbers for version-sensitive cards.
- Open and inspect the exported PDF rather than trusting the source document.
- Archive the source list, cleaned list, approved configuration, manifest, and final export.
The last check should be brutally simple: if you reopened this project six months from now, could you identify every card, version, quantity, and paired face without guessing? If the answer is yes, the batch is not merely printable. It is repeatable.
References
- PrintMTG
- PrintMTG
- How to Print a Moxfield Decklist Without Rebuilding the List by Hand – Print MTG Cards
- How to Archive a Finished MTG Proxy Project So You Can Reprint It Later – Print MTG Cards
- PrintMTG
- On Proxies, Policy, and Communication | MAGIC: THE GATHERING
- Magic: The Gathering Proxy Cards | PrintMTG