A print file that looks correct on your screen can still get rejected by a printer or self-publishing platform — missing bleed, the wrong trim size, or Arabic fonts that aren't properly embedded are the usual reasons. This is the check that catches it before submission, not after.
Every file is checked personally by Ata Rafi, Founder and Chief Formatter before it's marked ready to submit.
A print-ready PDF is a file that meets a specific set of technical requirements a printer or self-publishing platform checks automatically: correct bleed, trim size within tolerance, all fonts embedded, images at print resolution, and the right color mode. A file can look perfect on screen and still fail every one of these checks.
This is a different output from an ebook file. See Arabic eBook Formatting for EPUB and Kindle preparation — the two are generated from the same typeset source but follow completely different technical rules.
Anyone self-publishing a paperback or hardcover who needs the file to pass the platform's technical check on the first try.
Authors and publishers who've received a specific rejection reason from a platform and need the underlying file fixed, not just resubmitted.
Publishers and institutions sending a file directly to a commercial printer, where a rejected or misprinted run costs real time and money.
Anyone releasing a title in both formats who needs one typeset source to correctly produce both outputs.
A print file is rejected when it fails one of a small, fixed set of technical checks — almost always one of these five:
Artwork or background color doesn't extend far enough past the trim edge, leaving a thin white line after the page is cut.
The page dimensions don't match the platform's exact trim size within its allowed variance, so pages don't cut cleanly.
The PDF references a font instead of embedding it, so the printer's system substitutes a different one — a bigger risk for Arabic than Latin script.
Files submitted in RGB instead of CMYK print with shifted, inaccurate colors, especially on cover files.
Images below print resolution look sharp on a screen but come out visibly blurry or pixelated once printed.
Each of these maps to an exact number a platform checks against — not a judgment call. The actual figures are below.
These are the two most common self-publishing print destinations. Exact figures below are confirmed against each platform's current published specs before a file is delivered, since requirements can change on the platform's end.
Where a platform hasn't published a figure for something (KDP's image resolution, for example), the stricter or more commonly accepted standard is used rather than guessing.
Font substitution happens when a viewer or printer's system doesn't have the exact typeface a PDF calls for. This risk is higher for Arabic files because far fewer systems carry a Unicode-compliant Arabic typeface with correct ligature and diacritic support built in by default — so an unembedded or partially-embedded Arabic font is more likely to actually break on someone else's machine than an unembedded Latin font would be. See Arabic Font Selection & Licensing for how font choice and licensing work together.
This is checked directly: every font is confirmed as embedded (not just referenced) in Document Properties before a file is marked ready, specifically to catch the silent-failure case before it reaches a printer.
See the portfolio for examples of Arabic-script projects taken through to print.
Both are generated from the same typeset source file — the difference is the technical rules applied at export, not a separate manuscript.
Print-ready PDF preparation is included as part of the formatting process for any project headed to print — it's not billed as a separate add-on. See Pricing & Quote for what actually drives a project's quote.
A PDF that meets a printer or platform's exact technical requirements — correct bleed, trim size, embedded fonts, print resolution, and color mode — and will print correctly without being rejected or coming out wrong.
Almost always one of five things: missing or incorrect bleed, trim size outside the platform's tolerance, fonts not embedded, the wrong color mode, or images below print resolution. Note that KDP doesn't accept Arabic paperback submissions at all — see Can You Print an Arabic Book Through Amazon KDP? for why IngramSpark is the print route for Arabic.
Trim size is the final, cut dimensions of the page. Bleed is the extra margin of artwork or background color extending past the trim edge, so there's no thin white line if the cut shifts slightly during production.
Usually because the font wasn't properly embedded in the PDF, so the printer's system substituted a different one — which can break letter joining or drop diacritics. This risk is higher for Arabic than Latin script, since fewer systems carry a compatible Arabic typeface by default.
Yes — both are generated from the same typeset source, but print and EPUB/Kindle follow different technical rules. See Arabic eBook Formatting for the ebook side.
Yes — get in touch with the rejection reason from the platform, and the file is corrected against the specific spec it failed.
Need a cover? See Arabic calligraphy art for book covers.
Every file is checked personally before it's marked ready — not run through a script and shipped.
Request A Free Quote