What Files Does IngramSpark Accept? A Guide for Authors
For print books, IngramSpark accepts two production files: a print-ready PDF for the interior and a print-ready PDF for the full cover spread. For ebooks, it typically accepts EPUB. The file types are simple. What trips authors up is that "print-ready" means built to your book's exact specs, not just any PDF.
What files does IngramSpark accept for books?
Your cover spread file is not just the front cover. It has to include the back cover, spine, and front cover together, built to the exact trim size, page count, paper type, and binding you selected.
This is where most upload problems start. You can have the right file type and still have the wrong file setup. A Word document exported as a casual PDF is still a PDF, but it may not meet IngramSpark's print requirements. The platform isn't asking for any PDF. It's asking for a press-ready one.
For ebooks, the workflow is separate from print, with its own validation rules and its own ways to fail. If you're only publishing a paperback or hardcover, the file question is almost entirely about PDFs.
The interior file IngramSpark accepts
Submit your interior as a PDF matching the exact trim size you chose. If your book is set up at 6 x 9, the PDF pages need to be 6 x 9. Uploading a letter-size PDF and expecting it to resize cleanly sets you up for rejection or poor print results.
IngramSpark also expects embedded fonts, proper margins, and image resolution that holds up in print. Black-and-white and color interiors have different considerations, especially around ink coverage and color spaces. Grayscale images that work fine in one book may be inadequate in another, depending on your printing option and the visual demands of the project.
Page count matters too. Your PDF has to align with the binding method and paper choice, since spine width is calculated from page count and paper stock. Even a small interior edit after you build the cover can create a mismatch that's hard to spot on screen but enough to trigger a review problem.
Blank pages are fine if they're intentional, for front matter flow or to keep chapters starting on the right-hand page. What causes trouble is accidental pagination, inconsistent numbering, or content drifting outside safe margins.
The cover file IngramSpark accepts
The cover PDF is its own category of problem. It must be a full spread built from the exact production specs of your book, accounting for trim size, bleed, spine width, barcode area, and safe zones. If your cover was designed as a flat front image or as separate front and back files, it isn't ready yet. IngramSpark wants one continuous file.
The spine is where precision matters most. Change the page count, and the spine width changes. Change the paper type, and it changes again. Change the binding, and the whole geometry can shift. That's why you shouldn't finalize the cover until the interior is locked.
Images on the cover need enough resolution for print, and text should stay inside safe areas so it isn't clipped during trimming. Bleed should extend beyond the trim line where required. Text placed too close to the edge can pass your visual check and still print badly.
What IngramSpark does not want
IngramSpark doesn't want working files from your design software. That means no DOCX, INDD, PSD, or Canva source files as production files for print. Those are useful in your own workflow, but they aren't the final deliverables the printer uses.
It also doesn't want loosely assembled files that still need cleanup: a manuscript PDF with tracked changes, comments, hyperlink styling, low-resolution screenshots, or unembedded fonts. A cover exported from a web design tool without proper bleed and spine calculations isn't ready either.
This is the part that frustrates independent authors. You can do real work, spend real money, and still end up with a technically invalid file package. The issue is rarely effort. It's the gap between looking finished and being press-ready.
Print-ready means more than file type
A lot of advice online reduces this to "upload a PDF for print and an EPUB for ebook." That's incomplete. File type is only the first gate.
A print-ready PDF needs the right page size, embedded fonts, proper image quality, clean transparency handling, and layout choices that respect trim and binding. If any of those are off, the file may upload but fail later, or print with defects you only notice after ordering a proof.
Fix the issues that affect acceptance, print quality, and reader experience. Don't get stuck polishing details that won't materially change the book.
Common reasons accepted files still get flagged
Even with the correct file types, IngramSpark can still flag problems. The most common ones are trim size mismatches, missing bleed, font embedding failures, low-resolution images, oversized ink coverage, and cover dimensions that don't match the interior specs.
Transparency flattening and layer behavior cause trouble too. A cover may look correct in one app and export unpredictably in another. Fine lines can shift, drop shadows can rasterize poorly, and rich black settings can vary. These are production issues, not design taste issues, and they're exactly why file validation matters before upload.
Barcodes can also create trouble. If you supply your own barcode, placement and quiet space matter. If you use platform-generated options, your cover needs to leave room for them. A beautiful back cover that ignores barcode placement isn't actually finished.
Ebook files are different
If you're publishing an ebook through IngramSpark, EPUB is the usual accepted format. But EPUB success depends less on print geometry and more on structured content. Reflowable text, clean chapter navigation, valid metadata, and well-behaved image sizing matter more than fixed page design.
Some books translate well into EPUB with minimal adjustments. Others, especially heavily designed books or image-rich nonfiction, need extra work. If your book relies on precise layout, tables, sidebars, or fixed visual relationships, an EPUB can require compromises a print PDF doesn't.
How to prepare files without getting rejected
Finalize the manuscript first, lock the page count, choose your exact print specs, and only then generate the interior and cover files. Revisions after cover creation are possible, but they raise the chance of mismatches.
This is where a unified workflow saves time. If you're writing in one tool, laying out interiors in another, designing covers somewhere else, and checking retailer specs by hand, small errors compound. Forge lays out your manuscript and exports a print-ready PDF and a validated EPUB from the same source, so your interior and cover specs stay matched as you finalize the book.
Before upload, review your PDF exports at 200 percent or more. Check margins, image clarity, page order, blank pages, front matter, and spine text alignment. Then compare the cover specs against the final page count, not yesterday's draft.
So, what files does IngramSpark accept?
For print books, the working answer is a print-ready interior PDF and a print-ready full cover PDF. For ebooks, it's typically EPUB. But the real answer is stricter than that: IngramSpark accepts files that are not only in the right format, but built to the exact production specs of the title.
That distinction separates smooth uploads from expensive do-overs. Treat file prep as the final production step, not a basic export, and you keep control of your timeline, your print quality, and your launch.
Last updated November 13, 2026
← All posts