Preparing files for print

Print-ready files follow rules that screens never taught you, and manufacturers reject or misprint files that break them. The big four are bleed, safe zone, color mode, and resolution. Learn them once and every quote, proof, and print run goes smoother.

Bleed is extra artwork extending past the final cut line, typically about 3 millimeters (an eighth of an inch) on every edge. Cutting machines drift slightly, and bleed guarantees the drift shows more artwork instead of a white sliver. The safe zone is the opposite: keep all text and important elements a few millimeters inside the cut line, so nothing critical gets clipped. Every manufacturer publishes templates with these lines marked for each component, always design inside their template rather than guessing, because card sizes, box dielines, and punchboard layouts vary by factory.

Color is the other common trap. Screens display RGB light, presses print CMYK ink, and the CMYK gamut is smaller, so vivid screen colors, especially bright greens, blues, and oranges, print duller than they look on your monitor. Convert files to CMYK (or confirm the manufacturer's conversion process) and review a printed proof before approving a run. Resolution should be 300 DPI at final printed size. Art pulled from the web or upscaled from small files will print blurry no matter how sharp it looks on screen.

Before submitting, walk a preflight checklist: fonts outlined or embedded, images linked at 300 DPI, correct template per component, bleed on every edge, nothing important outside the safe zone, and file naming that matches the manufacturer's spec sheet. Then order a pre-production copy and inspect every component before approving mass production. Files are cheap to fix, a misprinted run of 2,000 games is not.

Video tutorials

Graphic Design for Board Game Designers!

How to Write a Plot for your Story [Writer's Dice - Kickstarter Video]

Reference tutorials and tools

Try it in Runner

Put this concept into practice. Build your game visually and playtest it in Tabletop Simulator, no code required.

Open your dashboard