This is for customers who want to submit their own custom files for us to print.
Note that we can generally work with any file that you send us, but to maximize the quality of the final product we recommend that you follow these guidelines.
If you need help, our talented graphic designers can assist, or you can use our web based tools to guarantee high quality prints with minimum effort.
TLDR
Best file to send: a print-ready PDF (bonus points if it’s PDF/X).
MTG card size: 2.5 x 3.5 in (63 x 88 mm). Add 0.125 in (3 mm) bleed on all sides if your art goes to the edge.
Images: 300 dpi at final size. Line art: aim higher (600–1200 dpi).
Color: CMYK, not RGB.
Fonts: embed them, or outline them (preferred when possible).
Links: no missing linked images. If you send native files, package everything.
Our preflight is technical only: we’ll check the file can print, not that your card says “teh” instead of “the.”
If you read nothing else, read the last bullet. It saves friendships.
Why we have file requirements at all
Our pre-press team can handle typesetting and custom design, but if you’re sending your own files, clean inputs mean fewer delays, fewer “quick questions,” and fewer moments where everyone pretends they are calm about a missing font.
We do run a preflight check before your job hits the RIP. That preflight confirms the file is technically printable. It does not proofread, fact-check, or gently tell you that your commander’s rules text is missing two words and your whole playgroup will notice.
What we check (and what we do not)
We check (technical)
File opens and processes cleanly
Page size, bleed boxes, and basic print readiness
Fonts are embedded or outlined
Linked images are present (or embedded)
Resolution is not obviously doomed
Color space is printable
We do not check (content/design)
Spelling, grammar, card names, or templating accuracy
Whether your “custom Black Lotus” is a joke or a life choice
Whether your art has rights/permission (that part is on you)
If you want the “we’ll handle the layout stress” route instead, use our MTG Card Maker and export from there.
Preferred file formats (Good, Better, Best)
Best
Print-ready PDF (PDF/X preferred)
This is the most reliable way to preserve sizing, font behavior, and layout consistency.
Better
Packaged native files + a reference PDF
If you’re sending Illustrator, InDesign, Photoshop, or Quark files, include:
the working file
fonts
linked images
a PDF you printed/exported as the “this is what it should look like” reference
Good
High-res PNG/TIFF for single card faces
Great for single-card uploads when they’re correctly sized and high resolution.
Please do not (unless you like chaos)
Low-res JPGs pulled from the internet
JPG can be fine when exported correctly, but “right-click save” images are usually tiny and compressed. The result is crunchy text and sadness.
Document setup for MTG proxies (size, bleed, safe zone)
Trim size (finished card size)
2.5 x 3.5 inches (about 63 x 88 mm)
Bleed (to prevent white edges)
If your art/background goes to the edge, add 0.125 in (3 mm) bleed on all sides.
That means your full canvas (with bleed) is about:
2.75 x 3.75 inches (about 69.9 x 95.3 mm)
Safe zone (keep important stuff away from the blade)
Keep critical elements (rules text, mana symbols, important art faces, etc.) at least 0.125 in (3 mm) inside the trim. Cutting is accurate, but it is not psychic.
Scaling
Build the file at 100% scale
When printing or exporting, avoid anything that says “fit to page” or “scale to printable area”
Pre-Press Checklist (the part you actually came for)
1) Fonts
Embed all fonts in the PDF (or include them if sending native files)
If possible, convert fonts to outlines (especially in Illustrator)
Avoid “mystery fonts” that came from a free download site in 2009 and have 14 different versions
2) Links and images
No missing links. Everything must be embedded, or included in a packaged folder
If using InDesign/Quark, Package/Collect for Output and send the whole folder
Do not rely on images “linked from your desktop.” Your desktop will not be available to our RIP (tragic, I know)
3) Color
Convert RGB to CMYK (RGB does not separate predictably for print)
Spot colors: clearly name/specify them (PMS if relevant)
Avoid accidental “almost black” mixes for body text
Black specifically (because black is where files go to lie):
For small text and thin lines, use 100% K (0/0/0/100)
For large black areas, rich black can be okay, but do not use it for fine type
Never use Registration as a fill color. That is how you create a four-ink swamp.
4) Resolution (at final size)
Photos/art: 300 dpi minimum at the size it prints
Line art/bitmap art: 600–1200 dpi recommended
Do not use web images unless you enjoy fuzzy mana symbols
Make sure placed/embedded images are not scaled up in layout (scaling up lowers effective dpi)
5) Transparency and effects
If your file uses lots of transparency, shadows, glow, etc., export carefully (PDF/X presets usually help)
If you see weird halos, flattened effects, or missing elements in your exported PDF, fix that before submission
6) Final sanity checks (because we don’t do them for you)
Accuracy and typography
Run spell check
Proofread names, numbers, and anything spell check will happily ignore
Fix punctuation (quotes, apostrophes, inch marks)
Check hyphenation and spacing (widows/orphans) if you’re doing multi-card text layouts
7) “If you can’t print it, we probably can’t either”
Before submitting:
Export your final PDF and print a test page at 100% scale
View the PDF at high zoom (400–800%) and confirm text is crisp
Confirm the page size and bleed are correct
How to package and submit your files
If you are sending a PDF
Send one print-ready PDF (or one per project/deck, if that’s cleaner)
Do not password-protect it
If you are sending native files
Zip a folder containing:
the document file
all fonts
all linked images
any notes (trim, bleed, quantities)
File naming (please, for the love of organization)
Use something descriptive:
OrderNumber_ProjectName_Version1.pdf
Lastname_CustomCommanderDeck_Feb2026.pdf
And if anything is unusual, tell us. “This is intended to print dark” is helpful. “Please make it pop” is… spiritually meaningful.
FAQs
Do I have to send a PDF/X file?
No, but it’s strongly preferred. A clean print-ready PDF exported with print settings and embedded fonts is usually fine. PDF/X just reduces surprise behavior in professional print workflows.
Can I send Photoshop files?
Yes, but we still prefer a print-ready PDF export (or a high-res TIFF/PNG if you’re delivering single images). If you send PSDs, make sure resolution and document size are correct and fonts are handled properly.
What if my files are in Word or Excel?
Export to PDF first. Office apps can reflow layouts in ways that are technically impressive and spiritually upsetting.
Will you fix my file if something is wrong?
We’ll tell you what failed preflight and what needs to change. We can help with most things, but if it will require a significant time investment, it may require an additional charge.
Why did my blacks print “washed out”?
Usually it’s one of these: RGB black, rich black used for fine text, low-resolution art, or a mismatch between what you saw on screen and how CMYK prints. Start with 100% K for text and CMYK output, then test.