If you’ve ever sleeved up a fresh batch of proxies and realized every card looks like it was printed through a sock, welcome. MTG proxy image quality usually doesn’t fail because you picked the wrong paper or because your printer “hates you personally.” It fails because the image file you started with was too small, too compressed, or quietly got resized into oblivion somewhere along the way.
The good news is this is fixable, and you don’t need a sacred printing ritual. You need the right resolution, a sane file format, and a little restraint with the “Save for Web” button.
MTG proxy image quality starts with pixels, not vibes
Here’s the part nobody wants to hear: your printer can’t print detail that isn’t there.
If your card front is a 488×680 image you grabbed from somewhere, and you print it at Magic size (about 2.5″ × 3.5″), you’re effectively printing at roughly 195 PPI. That’s not catastrophic for a poster viewed from across the room, but a card is something you hold 18 inches from your face while squint-reading rules text. So the printer or print service has to invent extra pixels (upsampling), and that’s where “fuzzy mud-cards” are born.
A quick rule that actually holds up:
- Target at least 300 PPI at final print size.
- If you’re including bleed (you should), you need more pixels than the trim size math suggests.
And yes, you’ll see people say “300 DPI” because the internet is like that. But what you actually control in an image file is PPI and pixel dimensions.
DPI vs PPI, or: two acronyms enter, clarity leaves
PPI (pixels per inch) is the resolution of your image file. DPI (dots per inch) is how a printer sprays tiny dots on paper. People mix them up constantly because both measure “stuff per inch,” and both make your eyes glaze over.
For proxy printing, the practical takeaway is simple:
- Pixel dimensions matter most.
- The “DPI” metadata in a file can be ignored by some workflows and treated as gospel by others. So don’t rely on metadata to save you. Build the image at the correct pixel size for the template you’re using.
If you want one mental model: PPI is what you bring to the party, DPI is how the printer serves it. If you show up with a sad little screenshot, the printer can only serve sad little screenshot.
The numbers that keep your proxies from looking like soup
For Magic-sized cards, many print services use “poker size” as the template. The trimmed card is 2.5″ × 3.5″, but your upload is usually larger because of bleed and safe areas.
A common requirement you’ll run into for poker-size cards is:
- Minimum upload size: 822 × 1122 pixels at 300 PPI (this includes bleed expectations)
That’s the “don’t make me scale your file” floor.
Here’s how to think about it:
- Trim size is the final card size after cutting.
- Bleed is extra image beyond the cut line so tiny cutter shifts don’t reveal white edges.
- Safe area is the “keep text inside here if you enjoy readable words” zone.
If your proxy tool or template expects 822×1122 and you upload 750×1050, it will still print, but it’ll be scaled up. Scaling up is where crisp edges turn into “soft vibes,” and small mana symbols start looking like modern art.
What about 600 PPI?
If you want to be extra (sometimes worth it for tiny text or very sharp frames), you can double the pixel dimensions. That means files around 1644 × 2244 for the same template. You won’t get twice the quality from the same bad source image, but you can preserve detail better if your source is genuinely high-res.
File formats: choose violence against compression artifacts
Your file format choice is a big part of MTG proxy image quality, because formats don’t just “store an image.” They store it with different tradeoffs: compression, color handling, transparency, and how badly they punish sharp edges.
PNG: the safe pick for crisp frames and text
PNG is lossless. It’s great for:
- Sharp borders
- Flat colors
- Text
- Icons (mana symbols, set symbols)
If your proxy has clean lines and readable rules text, PNG is your friend. File sizes can be bigger, but storage is cheaper than reprinting a deck that looks like it’s melting.
JPEG: fine for art, risky for everything else
JPEG is lossy. That means it throws away detail to shrink file size, and it loves to do it right where you least want it: around edges and in flat color areas.
Use JPEG if:
- You have a photographic or painterly image
- You save at high quality (not “medium,” not “email,” not “aggressively optimized”)
- You are not repeatedly re-saving the same JPEG over and over (each save can add damage)
JPEG is how you end up with halos around text, blocky gradients, and that “why is the black outline made of little squares?” experience.
PDF/TIFF: best when you control the pipeline
Some services accept PDF or TIFF. These are great if you’re building a full print-ready layout and want maximum control. PDFs can also embed vectors and fonts, which keeps text razor sharp.
The downside: some proxy workflows and auto-generators don’t love PDFs, and some services will rasterize them anyway. If your pipeline is “upload a single card front image,” PNG usually wins on simplicity.
What to avoid
- GIF for proxy card faces. Limited colors can wreck gradients and subtle shading.
- WebP unless you know your print service accepts it (many don’t). Convert to PNG or high-quality JPEG.
Why your proxies look muddy (and how to stop it)
Most “mud-card” problems come from a handful of repeat offenders.
1) Starting with low-res art
If your source image is small, you can’t upscale it into real detail. AI upscalers can sometimes help, but they can also invent textures that look fine at a glance and weird up close. That’s a trade.
If you care about MTG proxy image quality, you want a source that was already big enough to print cleanly at card size.
2) Resizing in the wrong direction
Downscaling (making a big image smaller) usually looks fine if done well.
Upscaling (making a small image bigger) is where blur enters the chat.
If your workflow includes placing an image into a template, check that it’s not being enlarged. “Fit” buttons are convenient. They are also liars.
3) Overcompression
If your JPEG looks “fine on screen,” zoom in to 200% and look at:
- The edges of text
- The border around the art box
- Any gradients
If you see blockiness, mosquito noise, or weird ringing around letters, that will print. Printing does not magically forgive compression sins. It simply commits them to paper.
4) Color space surprises
Most online images are in sRGB. Many print workflows convert colors for printing. That conversion can shift saturation and darken midtones.
Basic advice that avoids pain:
- Stick to sRGB unless your printer explicitly tells you otherwise.
- Don’t crank saturation to “make it pop.” It will pop right off the edge into “why is my forest neon?”
5) Sharpening at the wrong stage
If you sharpen before resizing, then resize, you can undo the sharpening.
If you resize first, then apply light sharpening, you usually get cleaner text and borders.
Go gentle. Oversharpening creates halos that look awful in print, and your card starts to resemble a deep-fried meme.
A boring checklist that prevents most proxy disasters
If you do nothing else, do these:
Use a template size that matches the print service (for poker-size cards, 822×1122 at 300 PPI is a common minimum).
Export as PNG when the card has sharp frames, small text, and flat colors.
If you must use JPEG, export at high quality and avoid re-saving multiple times.
Don’t upscale a small file and hope. Hope is not a production workflow.
Keep important text inside the safe area so minor cutting shifts don’t trim your rules text into modern poetry.
If you’re newer to proxies (or you just want the “casual play, not tournament drama” version of the conversation), start with All About MTG Proxy Cards. And if your group somehow turned “testing decks” into a parliamentary procedure, MTG: How the Stack Works pairs nicely with any table that loves rules precision.
Wrap up: crisp proxies are mostly math and self-control
You don’t need 9000 DPI. You need enough pixels for the physical size, a format that doesn’t mush your edges, and a workflow that doesn’t secretly enlarge your art like it’s trying to sabotage you.
Once you lock in the basics, MTG proxy image quality stops being mysterious. Your cards look like cards, your text is readable, and your deck no longer resembles a watercolor recreation of itself.
And honestly, that’s the dream: spend your time goldfishing hands, not troubleshooting why your Sol Ring looks like it was photographed from orbit.
