What is a KDP preflight checklist?
A KDP preflight checklist is a step-by-step validation workflow used before upload to confirm trim size, bleed, spine width, font embedding, and PDF export integrity.
KDP + IngramSpark Pre-Upload Engineering Checklist
Keyword-aligned guidance for KDP preflight, IngramSpark print validation, PDF export QA, bleed control, spine measurements, and validator message triage.If fonts keep showing as missing or unsupported, follow the Unsupported Font (Lucida) Incident.
Common submission failures include incorrect cover dimensions, bleed missing, spine mismatch, and fonts not embedded. Use this pre-upload checklist to catch those defects before submitting files to KDP or IngramSpark.
The broader release sequence for this workflow is documented in Print File Preflight Guide.
KDP preflight checklistIngramSpark cover validationPDF export QAcover bleed and spine controlvalidator message triagesubmission risk scan
What this checklist validates
Core checks that reduce first-pass rejection risk during platform preflight.
- trim size validation
- bleed control
- spine width checks
- font embedding
- PDF export integrity
The spec sheet behind those checks should be frozen first, and Book Printing Specifications is the clearest reference for that step.
Geometry & template alignment
Lock trim, bevel, and spine arithmetic so the panel layout matches what the printer expects.
- Match MediaBox, MediaHeight, and bleed to the latest template stats.
- Recalculate spine width whenever page count or paper weight shifts.
- Keep panels linear so spine/trim boundaries stay predictable.
Bleed, spine, and bleed tolerance
A uniform bleed and precise spine protect critical text from rejection.
- Apply a consistent 0.125" (3.2 mm) bleed around all panels.
- Respect spine art limits and recalculate bleeds when the page count shifts.
- Use Acrobat or preflight overlays to confirm the bleed visually extends past trim.
Fonts & resource compliance
Handling fonts right keeps you out of KDP’s unsupported font loop.
- Use pdffonts or Acrobat to ensure no Lucida or other flagged font remains.
- Replace decorative/system fonts with widely supported serif/sans families.
- Export a fresh PDF—avoid editing existing files and reusing old metadata.
Platform-specific preflight protocols
Six engineering-grade checks per platform plus metadata cues so you never re-export the wrong file.
KDP engineering checklist
- Trim size matches your interior settings (no accidental resize).
- Bleed is correct (usually 0.125 in / 3.2 mm) and backgrounds extend into bleed.
- Spine width is recalculated from final page count + paper type.
- Full-wrap cover PDF page size equals: back + spine + front + bleed.
- Text stays inside safe areas; nothing critical touches trim/spine folds.
- PDF export has no scaling (100%), correct page size, and clean edges.
Critical KDP metadata
- • MediaBox width must equal [Trim × 2 + Spine + 0.25"].
- • PDF version should be 1.3 or higher (PDF/X-1a recommended).
- • All images must be CMYK; RGB black (0,0,0) will convert to heavy 4-color ink.
IngramSpark engineering checklist
- Generated template matches final page count + paper + trim.
- Bleed is correct and backgrounds extend fully into bleed.
- Spine width matches template (regenerate if page count changes).
- Barcode/ISBN area is respected (white box + quiet zone).
- Text stays inside safe zones (front/back/spine).
- Export is single-page full-wrap PDF with no scaling or crop marks (unless explicitly allowed).
Barcode quiet zones
Keep the ISBN barcode area clear with a 2" x 1.2" white box. Transparent or low-contrast art near the barcode will repeatedly trigger the rejection logic.
Validator messages → corrective actions
Map the most common rejection text to the next best action.
| Validator | Class | First corrective action | Second corrective action |
|---|---|---|---|
| "File not print ready" (generic) | Mixed; often geometry first | Run full preflight report and inspect page boxes | Triage by blocker severity, not by message order |
| "Cover dimensions incorrect" | Geometry/template mismatch | Regenerate template for exact title settings | Rebuild cover spread from source guides |
| "Bleed missing or insufficient" | Geometry/export settings | Verify bleed values in source doc and export preset | Re-check BleedBox and visual overfill in Acrobat |
| "Fonts not embedded" | Resource compliance | Re-export with full embedding and subset policy | Replace problematic licensed fonts if needed |
| "Page count mismatch" | Structure | Compare PDF page count with title metadata | Re-export interior after pagination lock |
| "Spine text not allowed" | Policy threshold | Remove spine text for low page count titles | Re-layout cover hierarchy accordingly |
Related problem guides
If the visible symptom is a preview shift rather than a clear validator label, compare it with KDP Preview Layout Different.
Frequently asked questions
FAQ content powers the reusable schema and answers top search intent.
Does this checklist help both KDP and IngramSpark submissions?
Yes, the checklist codifies the shared geometry, bleed, and PDF/X-1a requirements so you can reuse the same protocol across both networks.
What if fonts-not-embedded persists even after embedding Lucida?
Run pdffonts or Acrobat, replace Lucida variants with supported serif/sans options, and follow the Unsupported Font (Lucida) Incident workflow to reset the validation state.
→ Unsupported Font (Lucida) IncidentHow often should I rerun the checklist?
Revisit it after every source edit, template update, or export iteration; treat it as a gating step before each upload.
Why do I still see rejection after the bleed/spine specs pass?
Residual failures are often due to PDF version, transparency flattening, or font flags—use the validator message table and related problem guides to chase the underlying cause.
What This Tool Does
Pre Upload Checklist is an interactive tool for validating one specific part of the print-production workflow before upload. It turns publishing specifications into a concrete output so you can confirm the file or calculation before the platform flags the issue.
When the package fails specifically on edge extension, the direct problem page is KDP Bleed Missing.
If the cover side of the checklist is the main risk area, keep KDP Cover Size Guide open while reviewing geometry.
When You Need This Tool
Use this tool when the source file, template, or export settings are still being finalized and you need a reliable answer before submitting the PDF. It is most useful after a specification changes and before you commit to a new upload.
When local checks pass but the parser still rejects the package, compare the state with KDP Upload Processing Error.
Reference Reading
Supporting References for This Workflow
Use these references to understand the surrounding workflow and diagnosis context before moving to the action path below.