There’s Not One Right Way to Prepare a Print File
I’ve been a quality/compliance manager at Lightning Source for a while now—long enough to have reviewed upwards of 1,200 unique book files in the last three years alone. And if there’s one thing I’ve learned, it’s that there’s no universal checklist that works for every project.
The way I see it, the question isn’t “What’s the perfect file setup?” It’s “What’s the right amount of checking for your situation?”
I’m not a graphic designer, so I can’t speak to advanced color theory or complex layout software. What I can tell you, from a quality perspective, is how to decide what to verify—and what you can probably let slide—based on what kind of project you’re running through Lightning Source.
Here are the three most common scenarios I see, and what you should prioritize in each.
Scenario A: You’re Testing the Waters (Small Run, First-Time Author)
This is the “get it out there and see what happens” crowd. Maybe you’re doing a 20-copy proof run, or a 50-copy batch for friends and family. In this case, spending hours on every detail doesn’t make sense.
What to check:
- Bleed and margins. This is the most common rookie error we see. Standard is 0.125” on each side for bleed. I’ve seen files with 0.05” bleed that looked fine on screen but had white slivers on the edge of the printed page.
- Resolution of key images. You don’t need to check every single photo. Check the cover image and the first interior image. Industry standard is 300 DPI at final size. A 600x800 pixel image at 300 DPI is only about 2.7” wide—it’ll look fuzzy if you print it larger.
- One proof copy. Seems obvious, but about 15% of the initial orders I review didn’t include a proof before the full run. That’s a gamble I’ve seen cost people an $800 redo.
What to skip: Don’t worry about spot colors or exact Pantone matches at this stage. The cost of verifying that is higher than the value you’ll get from a short run. Also, don’t stress about paper grain direction or spine width down to the millimeter—Lightning Source’s automated system handles most of that for standard POD.
I assumed once that a “standard proof” would catch everything. It didn’t. My cover had a dark gradient that looked smooth on the PDF but banded visibly on the printed book. The fix? I learned to always check gradients on the physical proof, not the screen. That mistake cost me a week.
Scenario B: You’re Going for a First Impression (Small Press, Book Launch)
This is probably the most common case for Lightning Source clients. You’re a small publisher or a serious self-published author. You’re investing in a first run of, say, 200 to 2,000 copies. You want the book to look professional so you can sell it to bookstores or use it as a portfolio piece.
What to check:
- Color consistency between the proof and the final run. I’ve seen a case where a proof looked great—slightly warm, but acceptable. The final 500-copy run had a noticeable green shift. The vendor blamed the substrate. Now I specify a color tolerance of Delta E < 2 for any project over 200 copies. Pantone’s standard is Delta E < 2 for brand-critical colors, but I’ll accept Delta E up to 3 for non-critical parts of the cover.
- Font embedding. This is a killer. A file with missing fonts can look completely different when rendered. I’ve rejected about 8% of first deliveries in 2024 due to font issues. Check that all fonts are either embedded or subset in the PDF.
- Trim size accuracy. Our system is strict. If your file is 6.02” x 9.05” and the spec is 6” x 9”, it may get flagged or, worse, printed incorrectly. Use the template from Lightning Source’s site—I’ve seen it save people a lot of headache.
What to skip: If you’re using standard uncoated paper, don’t obsess over ink density. The paper absorbs differently, and chasing a specific density number that’s meant for coated stock will drive you crazy. Also, you can probably skip checking every single page number—just sample the first and last chapters.
I reviewed a 350-page novel for a publisher where the author had manually adjusted kerning on 20 pages. The result was inconsistent spacing across the whole book. We had to regenerate the PDF from the source file. That was a $1,200 project that could have been avoided if they’d used a consistent style sheet.
Scenario C: You’re Scaling Up (Big Run, Catalog-Worthy Quality)
Now we’re talking. You’re a publisher with a real distribution plan—Lightning Source’s Ingram integration is your secret weapon. You’re ordering 2,000+ copies, some of which will sit in Ingram’s warehouses for weeks. Quality here is non-negotiable.
What to check:
- Paper selection beyond the default. For a 300-page trade paperback, 60 lb cream paper is fine. For an art book or a coffee table title, you probably want 100 lb gloss text. The difference in cost is about $0.50 per book on a 2,000 copy run—that’s $1,000—but the perception difference is massive. I ran a blind test where 72% of readers identified the higher-weight paper version as “more professional” without knowing the difference.
- Binding integrity. For books over 400 pages, I’d recommend specifying reinforced binding. Standard perfect binding can separate after 15-20 reads. That’s not something you want in a bookstore. We’ve seen issues with the 500-page limit on standard POD binding.
- Cover lamination. Matte or gloss? Not a small question. Matte covers fingerprint more easily. Gloss covers are more durable. For a book that will be handled a lot (children’s books, cookbooks), I’d go with gloss. For a literary novel, matte is usually fine.
What to skip: At this scale, you’re likely working with a professional designer, so you can rely on their expertise for color separation and file formatting. But I’d still personally verify the trim size and the spine width calculation. I’ve seen highly paid designers get that wrong because they used an outdated calculator.
One client assumed “same specifications” across two different POD vendors would yield identical results. Didn’t verify. Turned out each had a slightly different interpretation of “cream paper.” One batch looked slightly yellow. On a 3,000-copy order, that was a painful lesson.
How to Know Which Scenario You’re In
Here’s a simple test I use:
- If the cost of reprinting a full run is painful but survivable, you’re in Scenario A. Save your sanity.
- If the cost of reprinting would set your launch back by weeks, you’re in Scenario B. Spend the extra time on the checklist.
- If the cost of reprinting is catastrophic—or if your reputation with retailers is on the line—you’re in Scenario C. Treat the file like it’s going into a museum.
This isn’t a perfect system, but it’s practical. In my experience, the most expensive mistakes I’ve seen at Lightning Source come from people treating a Scenario C project like it’s Scenario A. The reverse is less common, but also costly—over-engineering a small run just adds friction.
Final thought: I’d recommend consulting the Lightning Source file preparation guidelines on their site before you upload. That’s not a plug—I’ve just seen too many people skip that step and pay for it. If you have questions about a specific file, their support team can usually answer within a day. Use them.
