What Files Does IngramSpark Accept?

If you are asking what files does IngramSpark accept, you are usually one step away from upload day - and one formatting mistake away from a delay. IngramSpark is strict in ways that surprise first-time publishers. The good news is that the accepted file types are straightforward once you separate the interior from the cover and understand what “print-ready” actually means.

What files does IngramSpark accept for books?

For most print books, IngramSpark accepts two primary production files: a print-ready PDF for the book interior and a print-ready PDF for the full cover spread. That cover spread is not just the front cover. It includes the back cover, spine, and front cover in one single file built to the exact trim size, page count, paper type, and binding you selected.

This is where many upload problems start. Authors often have the right file type but 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 is not asking for any PDF. It is asking for a press-ready one.

For ebooks, IngramSpark typically accepts EPUB files. That is a separate workflow from print, with different validation rules and different failure points. If your focus is a paperback or hardcover, the file conversation is almost entirely about PDFs.

The interior file IngramSpark accepts

Your interior file should usually be submitted as a PDF. It needs to match the exact trim size you chose for the book. If your book is set up at 6 x 9, the PDF pages must be 6 x 9. If you upload a letter-size PDF and expect the platform to resize it cleanly, you are setting yourself 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 interiors and color interiors have different production considerations, especially around ink coverage and color spaces. Grayscale images may be fine in one book and inadequate in another. It depends on the printing option you selected and the visual demands of the project.

Page count matters too. Your PDF has to align with the binding method and paper choice. A spine width is calculated from page count and paper stock, so even a small interior edit after you build the cover can create a mismatch. That mismatch will not always look dramatic on screen, but it can be enough to trigger a problem during review.

Another detail authors miss is blank pages. Some books need them for proper front matter flow or to keep chapters starting on the right-hand page. Those blank pages are fine if they are intentional. What causes trouble is accidental pagination, inconsistent numbering, or content drifting outside safe margins.

The cover file IngramSpark accepts

When people ask what files does IngramSpark accept, they often think the answer is just “PDF.” Technically yes, but the cover PDF is its own category of problem. It must be a full spread built from the exact production specs of your book.

That means the file has to account 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 is not ready yet. IngramSpark wants one continuous file.

The spine is where precision matters most. If your page count changes, the spine width changes. If your paper type changes, the spine width changes. If your binding changes, the entire geometry can shift. This is why experienced publishers do not finalize the cover until the interior is locked.

Images on the cover should be high enough resolution for print, and text should stay inside safe areas so it is not clipped during trimming. Bleed should extend beyond the trim line where required. If you place critical text too close to the edge, it may pass your visual check and still print badly.

What IngramSpark does not want

IngramSpark does not want working files from your design software. That means you are not uploading DOCX, INDD, PSD, or Canva source files as production files for print. Those may be useful in your own workflow, but they are not the final deliverables the printer uses.

It also does not want loosely assembled files that still need cleanup. A manuscript PDF with tracked changes, comments, hyperlink styling, low-resolution screenshots, or unembedded fonts is not ready. Neither is a cover exported from a web design tool without proper bleed and spine calculations.

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 is usually the gap between looking finished and being press-ready.

Print-ready means more than file type

A lot of bad advice online reduces this topic to a simple answer: upload a PDF for print and an EPUB for ebook. That answer is 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 worse, print with defects you only notice after ordering a proof.

That trade-off matters. Some authors rush to publish and treat proofing as optional. Others spend weeks tweaking files for issues readers would never notice. The smarter approach is controlled accuracy. Fix the issues that affect acceptance, print quality, and reader experience. Do not get stuck polishing details that do not materially change the book.

Common reasons accepted files still get flagged

Even when you use 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 do not match the interior specs.

Another common issue is transparency flattening and layer behavior. A cover may look correct in one app and export unpredictably in another. Fine lines can shift. Drop shadows can rasterize poorly. Rich black settings can vary. These are production issues, not design taste issues, and they are 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 is not actually finished.

Ebook files are different

If you are 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.

That creates a practical decision point. 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 that a print PDF does not.

How to prepare files without getting rejected

The safest workflow is to finalize the manuscript first, lock the page count, choose the exact print specs, and then generate the interior and cover files from those fixed decisions. Revisions after cover creation are possible, but they increase the chance of mismatches.

This is also where a unified workflow saves time. If you are writing in one tool, laying out interiors in another, designing covers somewhere else, and checking retailer specs by hand, small errors compound. A platform like Tunmire is built to reduce that friction by keeping drafting, design, formatting, and validation in one system. The practical benefit is simple: fewer preventable file issues before you ever reach IngramSpark.

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 is 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 is what separates smooth uploads from expensive do-overs. If you treat file prep as the final production step instead of a basic export, you keep control of your timeline, your print quality, and your launch. Self-publish without the rejections starts long before you click upload.