Google Docs handles the writing phase of a book perfectly well, but it cannot produce a print-ready interior file for most standard book trim sizes. It has no gutter or mirrored-margin setting, no bleed setting, and no section-level page numbering. Authors who draft in Google Docs will need to move the manuscript into Microsoft Word or a dedicated formatting tool before uploading to a print-on-demand platform.
- Can Google Docs Set a Custom Trim Size for Your Book?
- Does Google Docs Support Mirrored Margins or a Gutter?
- Will KDP Accept a PDF Exported from Google Docs?
- Can Google Docs Produce a Valid EPUB for Ebook Retailers?
- How Does Google Docs Compare to Word for Book Formatting?
- When Should You Move to a Dedicated Formatting Tool?
- Frequently Asked Questions
Can Google Docs Set a Custom Trim Size for Your Book?
Not for most book sizes. Trim size is the finished width and height of a printed book, and it has to match exactly what you selected when you set the title up. Google’s own documentation for changing page settings lists four things you can adjust under File > Page setup: orientation, paper size, margins, and page colour. Paper size is a dropdown of standard office and ISO sheet sizes rather than a field you type dimensions into.
That matters because the common trim sizes for fiction and nonfiction are not office paper sizes. KDP publishes a table of 16 paperback trim sizes, of which five are classed as regular and eleven as large; the smallest is 5.06" × 7.81" and the largest is 8.27" × 11.69". Hardcover offers five. The three sizes most indie novels use, 5" × 8", 5.5" × 8.5" and 6" × 9", are none of them standard paper sizes, so none of them appear in the Google Docs dropdown.
The A4 exception, and why A5 is not the workaround
There is one genuine overlap worth knowing about. A4 measures 8.27" × 11.69", and that exact size is on KDP’s published paperback list, as a large trim size. If you are producing a workbook, a large-format nonfiction title or anything else that suits A4, Google Docs can set the page size correctly, because A4 is in the dropdown.
A5 is a different story, and it is the workaround authors are most often pointed towards. A5 measures 5.83" × 8.27", which is close to 6" × 9" without being it. It does not appear anywhere on KDP’s trim size table, so a file set to A5 matches no trim size you can actually select. A mismatch of a fraction of an inch is enough to shift every margin, move the text block off centre and throw out the spine calculation on the cover. For print, the page size in your source file has to be the trim size, not near it.
Does Google Docs Support Mirrored Margins or a Gutter?
No. Print book interiors need mirrored margins, sometimes called facing pages, so that the inside margin on a left-hand page mirrors the inside margin on the right-hand page. That inside margin is the gutter: the extra space that keeps text clear of the binding. Without it, the words closest to the spine curve into the fold and become hard to read.
Google Docs applies the same margins to every page. Its page-setup documentation describes a single set of margin values, with no option to alternate left and right and no separate gutter field.
The gutter is not a fixed number, which is what makes the absence awkward. It scales with page count, because a thicker book curves more deeply at the spine. KDP publishes minimums by band:
| Page count | Minimum inside (gutter) margin | Minimum outside margins, no bleed | Minimum outside margins, with bleed |
|---|---|---|---|
| 24 to 150 | 0.375" (9.6 mm) | 0.25" (6.4 mm) | 0.375" (9.6 mm) |
| 151 to 300 | 0.5" (12.7 mm) | 0.25" (6.4 mm) | 0.375" (9.6 mm) |
| 301 to 500 | 0.625" (15.9 mm) | 0.25" (6.4 mm) | 0.375" (9.6 mm) |
| 501 to 700 | 0.75" (19.1 mm) | 0.25" (6.4 mm) | 0.375" (9.6 mm) |
| 701 to 828 | 0.875" (22.3 mm) | 0.25" (6.4 mm) | 0.375" (9.6 mm) |
Read those as floors rather than targets. A 320-page novel set at exactly 0.625" will pass KDP’s checks and still read tightly at the spine; most typeset books sit comfortably above the minimum, and we have written separately on setting print-on-demand page margins in Word. Other printers publish their own figures, so check the specification for the platform you are actually using rather than assuming KDP’s numbers apply everywhere. IngramSpark, for instance, recommends a 0.5" safety area on all sides of the text block in its File Creation Guide, expressed as a single recommendation rather than a table keyed to page count.
Microsoft Word has a “Mirror margins” option and a separate gutter field in Page Setup, which is the main reason Word remains the minimum viable option for authors formatting a print interior themselves without buying specialist software.
Will KDP Accept a PDF Exported from Google Docs?
KDP will accept any PDF upload and attempt to process it. Whether it passes review is a separate question, and a Google Docs export has several characteristics that cause problems:
- Wrong page dimensions. Unless your book is A4 or another size in the dropdown, Google Docs cannot output a PDF at the trim size you selected during title setup. This is the failure that stops the file outright.
- No bleed area. Bleed is extra image area beyond the trim line, so that a picture printed to the edge of the page still reaches the edge after the paper is cut. KDP trims 0.125" (3.2 mm) from the top, bottom and outside edges, so a bleed file needs the page size increased to suit. For a 6" × 9" book that means setting the page to 6.125" × 9.25". Google Docs has no bleed setting, so you cannot build that file.
- No section-level page numbering. Print convention puts front matter in roman numerals and the body in arabic, restarting at 1. That needs section breaks with independent numbering, which Google Docs does not offer.
Colour space is the point most often overstated, so it is worth being precise. IngramSpark’s File Creation Guide gives CMYK as the required colour space for print files, alongside 300 ppi and a 175 line screen. We could not trace an equivalent requirement in KDP’s own documentation: its guidance recommends CMYK and warns against mixing colour spaces within one file, but we found nothing stating that an RGB interior is rejected. Google Docs exports RGB only, which is a real constraint for IngramSpark and not usually the thing that fails a KDP upload.
Font embedding is similarly worth stating carefully, because “subset” sounds like a problem and is not one. IngramSpark’s File Creation Guide asks you to open the PDF in Acrobat and check File > Properties > Fonts, where either “(Embedded)” or “(Embedded Subset)” next to every font is acceptable. A subset simply means only the characters actually used were included. What gets a file rejected is a font that is not embedded at all.
Where IngramSpark genuinely rules Google Docs out is the file standard. Its File Creation Guide requires interior and cover PDFs to be PDF/X-1a:2001 or PDF/X-3:2002 compliant, a print-industry standard that fixes colour and font handling so the file prints identically everywhere. That setting lives in Adobe Acrobat Pro and in layout applications such as Adobe InDesign and Affinity Publisher. No word processor exports it, Word included.
Can Google Docs Produce a Valid EPUB for Ebook Retailers?
It can produce a file, but a rudimentary one. EPUB sits in the File > Download menu in Google Docs, alongside DOCX, RTF, TXT, PDF, ODT and zipped web page, listed as “EPUB Publication (.epub)”.
The resulting file carries minimal styling and takes its structure from whatever heading styles the document happened to use. In practice that means chapter openings only navigate correctly if you applied Heading 1 consistently, images come through at the resolution they were inserted at rather than print quality, and anything decorative, from drop caps to ornamental scene breaks, does not survive. Retailers differ in how much of that they tolerate, which is why an export can look fine on one device and wrong on another. We have written separately about why an EPUB can pass Kindle and fail Apple Books, and a word-processor export is one of the more common ways to end up in that position.
For an ebook that renders consistently everywhere, the usual routes are Calibre or Sigil (both free), Vellum or Atticus (both paid), or a formatting service.
How Does Google Docs Compare to Word for Book Formatting?
Microsoft Word is not a dedicated book design application either, but it carries the minimum feature set for a print interior. These are the differences that decide whether a file can be produced at all:
| Feature needed for a print interior | Google Docs | Microsoft Word |
|---|---|---|
| Custom page size at book trim dimensions | Dropdown of standard paper sizes only | Any dimensions you type in |
| Mirrored margins and a gutter field | Neither | Both |
| Section breaks with independent numbering | Page breaks only | Next Page, Even Page and Odd Page section breaks |
| Different headers and footers per section | One configuration per document, plus a different first page | Independent headers and footers in each section |
| Bleed setup for edge-to-edge images | No bleed setting | Achievable by enlarging the page size manually |
| PDF export | RGB, no PDF/X option | Embedded fonts and accurate dimensions; no PDF/X without an add-in |
Neither tool produces a PDF/X-compliant file, so neither suits IngramSpark without a further step through Acrobat. For KDP, a Word file with the page size set correctly passes review reliably. KDP publishes its own guidance on converting a paperback Word file to PDF if you want its recommended export route.
If you have already written your manuscript in Google Docs, moving to Word is straightforward: download as .docx, open in Word, then format. You lose nothing from the writing phase by starting in Google Docs. The judgement is about when to move rather than whether to start there. For a fuller picture of what the formatting stage actually demands, see our guide to the skills you need to format your own book for print.
When Should You Move to a Dedicated Formatting Tool?
The right moment to leave Google Docs depends on your book’s complexity and your target platforms.
For simple fiction with no images and a standard layout, you can stay in Google Docs until the manuscript is written and edited, then move to Vellum, Atticus or Word for the formatting pass. Nothing in the writing or editing phase requires print-specific settings, and drafting somewhere with good commenting and version history is a real advantage.
For nonfiction with images, tables or diagrams, move earlier. Image placement, text wrapping and caption styling behave differently in every application, so a complex layout rebuilt in a new tool is usually slower than one built there in the first place.
For anything published to both print and ebook, a purpose-built tool earns its cost. Vellum and Atticus generate print PDF and EPUB from one source file, which keeps the two formats consistent and saves maintaining separate documents. The trade-off is money and a learning curve: Vellum is macOS only and sold outright, Atticus runs in a browser, and both charge more than the nothing that Google Docs and an existing Word licence cost you.
Google Docs remains an excellent place to write and edit. Real-time commenting, suggestion mode and sharing make it easier to work with editors and beta readers than Word, and the safest workflow for most self-published authors is exactly that: draft and edit in Google Docs, export to .docx, then format elsewhere. The files that reach us for repair having been laid out entirely in a word processor almost always share the same fault, and it is not the one authors expect. The page size is usually right, because that is the setting everyone checks. What is missing is the gutter, so the text block sits centred on every page and slides towards the spine on alternate pages once the book is bound.
You cannot format a book for print in Google Docs, but you can certainly write one there, and that distinction is the whole of the answer. Google Docs is a writing tool that happens to make documents, not a book design tool. Write in it if it suits you, then export to .docx and set the trim size, gutter and section numbering somewhere that has those controls. The one case where Google Docs can produce a correctly sized page is A4, which is a KDP trim size in its own right; for 5" × 8", 5.5" × 8.5" or 6" × 9", the page size simply is not available to set.
Frequently Asked Questions
Can I use Google Docs to format a book for KDP?
You can write and edit in Google Docs, but for most trim sizes you cannot produce a print-ready PDF from it, because the page size you need is not in the paper size dropdown and there is no gutter setting. Export to .docx and finish in Word or a dedicated formatting tool. The exception is A4, which Google Docs can set and which is on KDP’s published paperback trim size list.
Is A5 close enough to 6" × 9" for a print book?
No. A5 is 5.83" × 8.27", and it is not one of the trim sizes KDP publishes, so there is nothing to select that matches a file set to A5. Even a fraction of an inch of difference shifts your margins, moves the text block off centre and throws out the spine width calculated for the cover. The page size in your source file has to be the trim size exactly.
What is the best free alternative to Google Docs for book formatting?
LibreOffice Writer is free and supports custom page sizes, mirrored margins and section-based formatting, and it exports PDFs at exact trim dimensions. For ebook work, Sigil (an EPUB editor) and Calibre (a converter) are both free and open source. None of them exports PDF/X, so none is sufficient on its own for IngramSpark.
Does Google Docs support headers that alternate between chapter title and book title?
No. Google Docs allows one header configuration for the whole document, with an optional different first page. It cannot alternate headers by section or set different content on odd and even pages, which is the standard arrangement in printed books.
Does a font subset in my PDF mean the fonts are not embedded properly?
No, a subset is fine. IngramSpark’s File Creation Guide asks you to open the PDF in Acrobat and look under File > Properties > Fonts, where either “(Embedded)” or “(Embedded Subset)” beside every font is acceptable. A subset just means only the characters your book actually uses were included, which keeps the file smaller. A font showing neither label is the one that gets a file rejected.
Is it worth learning Word just for book formatting?
If you plan to publish several books and want to format them yourself, learning Word’s page layout features is a reasonable investment, and it is the cheapest route to a file that KDP will accept. Dedicated tools such as Vellum and Atticus have a gentler learning curve for book-specific tasks and produce more polished results with less manual work, but they cost money and give you less control over the finer points of the layout.
