How to Format a Bilingual or Dual-Language Book (2026)

If you have translated your manuscript — or written it in two languages from the start — the next challenge is formatting, and bilingual book formatting is one of the trickiest layout problems in self-publishing. Every decision has to work twice: once for each language, on the same page, without confusing the reader. For bilingual picture books, our children’s picture book formatting guide covers the illustration side. This 2026 guide covers the rest: the four dual-language layouts, two-script typography, right-to-left handling, and the print and eBook rules that keep both languages reading cleanly.

By the end, you will know how to choose between facing-page, interleaved, column, and split-edition layouts; how to pick fonts that cover both of your languages; and the metadata and file-setup pitfalls unique to dual-language books.

What Bilingual Book Formatting Actually Means

A bilingual or dual-language book contains the complete text of a book in two languages — not a book with a few foreign words sprinkled in. Every sentence exists twice. The reader might be a language learner comparing the two versions line by line, a bilingual parent reading to a child, or someone in a diaspora community who wants the story in both their heritage language and the language of the country they live in. That comparison is the whole point of the book, so the formatting job is to make it effortless.

The core difficulty is that translations are never the same length. Spanish runs roughly 20 to 30 percent longer than English; German is longer still; Chinese is usually more compact. A paragraph that fills five lines in English might fill seven in Spanish — and your layout has to absorb that difference on every page. Paragraph-by-paragraph alignment is the standard solution: the same unit of thought appears in both languages at the same place on the page or spread, so the eye can jump back and forth. In the US, Spanish-English is the biggest bilingual segment, but the same principles apply to French, Arabic, Chinese, Hindi, Urdu, and every other pairing — what changes is the script, the reading direction, and the font support.

Choose Your Layout: The Four Dual-Language Approaches

Every bilingual book uses one of four layout approaches. Pick yours before you format a single page, because switching mid-project means rebuilding everything.

Facing pages puts language A on the left-hand (verso) page and language B on the right-hand (recto) page. This is the classic format for literary translations, language-learning texts, and poetry — each language gets a full page of breathing room and comparison feels natural. The cost is page count: roughly twice as long as a single-language edition, which raises print costs, and both languages must break chapters at the same place.

Interleaved paragraphs alternate one paragraph in language A with its translation in language B down the page. This is the best choice for reflowable eBooks, where facing pages do not exist, and it suits short texts like poetry collections and phrasebooks. Distinguish the languages clearly — regular type for the primary language and italics for the translation is the standard convention. On long texts it grows monotonous, so keep interleaved books under about 150 pages.

Side-by-side columns place two columns, one per language, on a single page. This works only in wide formats — landscape picture books, large-trim workbooks, or fixed-layout eBooks where you control the page exactly. Never attempt columns in a reflowable eBook or a standard 6 by 9 paperback; they collapse into unreadable narrow strips.

Split editions are two separate books, one per language, often sold as a set. This is the right commercial call when one language’s market dwarfs the other or the second script would complicate your main edition.

Typography for Two Scripts

Your font must contain every character in both languages — not most of them, all of them. A font that handles English beautifully can still be missing accented characters like ñ, ü, or č, and it will almost certainly be missing entire scripts like Arabic or Devanagari. The symptom is the tofu box: a hollow rectangle where a character should be. Search your finished PDF for these boxes before you upload anything.

The safest approach is a single font family with broad script coverage. Google’s Noto family — short for “no tofu” — was designed to cover every Unicode script without missing glyphs, with matched serif and sans-serif designs that look professional in print.

Do not assume the same point size looks the same in both scripts. Non-Latin scripts often read smaller at identical sizes: Arabic and Devanagari can need an extra half to full point to match the visual weight of Latin text. Print a sample page at actual size and adjust until the two blocks look like equals. Give mixed-script text generous leading too — 1.3 to 1.4 line spacing instead of the 1.15 to 1.2 that works for English alone — because stacked diacritics collide with the line above at tight spacing.

Keep the styling parallel as well: if chapter titles are 18-point bold in English, they are 18-point bold in the second language. Readers compare the two versions constantly, and any styling difference reads as an error even when it is intentional.

Handling Right-to-Left and Mixed Scripts

If one of your languages is Arabic, Hebrew, Urdu, or Persian, you are dealing with right-to-left (RTL) text. RTL paragraphs must be explicitly set to right-to-left direction — never faked with alignment buttons. In Word, use the paragraph direction control; in EPUB, use the dir=“rtl” attribute. Set correctly, punctuation, numbers, and embedded English words flow properly through the Unicode bidirectional algorithm. Set wrong, periods jump to the wrong end of sentences — errors your RTL readers will spot instantly.

Mixed-script lines need the same care. A Spanish sentence quoting an Arabic phrase is handled automatically as long as the base paragraph direction is correct — never try to fix ordering with manual spaces or line breaks.

Think about the physical object too. A book whose primary language is RTL traditionally opens from the right, with the spine on the right-hand side. Build your print PDF so the reading order runs right to left, and mention the reading direction in your book description — it prevents confused reviews from readers who opened the book “backwards.”

Print Formatting Rules for Dual-Language Books

For facing-page layouts, consistency is everything. Decide once which language goes on the left (verso) and which on the right (recto), and never deviate — the usual convention is the original language on the left, the translation on the right. Use mirror margins so the gutter stays on the binding side.

Embed and subset all fonts in your print PDF — non-negotiable for bilingual books. KDP and IngramSpark both require embedded fonts, and non-Latin scripts are the most common cause of embedding failures. Export with embedding turned on, then verify in a PDF reader that every typeface shows “Embedded Subset.” A PDF that looks perfect on your screen can print with substituted fonts or blank boxes on the printer’s system.

Choose your trim size with two languages in mind. A 6 by 9 inch trim that feels spacious for an English novel can feel cramped when every spread carries a longer translation. Many bilingual books move up to 7 by 10 inches; bilingual picture books commonly use 8.5 by 8.5 or 8 by 10 inches. Facing pages roughly double your page count, which directly raises print cost — check your royalty math before you commit.

Keep structural elements synchronized: chapters must start at the same point in both languages, inserting blank padding pages where one language runs short, and front and back matter should exist in both languages. For ISBNs, the simplest path is a single ISBN for the combined bilingual edition — one product, one listing, one barcode. Decide this before you finalize the copyright page.

eBook Formatting: Reflowable vs Fixed Layout

Your layout choice dictates your eBook format. Interleaved paragraphs belong in a standard reflowable EPUB: the two languages flow one after another, readers resize text freely, and the file works everywhere. Mark each paragraph’s language with the lang attribute (lang=“en”, lang=“es”) so screen readers pronounce each passage correctly.

Facing pages or side-by-side columns need fixed layout. Fixed-layout EPUB locks every element in place, preserving your spreads exactly — the right choice for illustrated bilingual children’s books and workbooks, though text cannot be resized and the file only shines on tablets. Our fixed-layout versus reflowable eBooks guide walks through the decision in detail, and our EPUB versus MOBI versus PDF comparison explains which file format to deliver where.

Three eBook-specific rules. First, embed your fonts in the EPUB instead of relying on device defaults, which frequently lack your second script’s characters. Second, test on real devices — a Kindle e-ink reader, a tablet, and a phone — because font rendering and RTL support vary. Third, if illustrations have text baked into the images, include both languages in the artwork or duplicate the illustrated pages per language; an image containing only English text inside a bilingual book reads as unfinished.

Publishing and Metadata for Bilingual Books

Bilingual books need bilingual metadata. KDP’s title setup has a single primary Language field — set it to your main audience’s language. Then work both languages into everything else: translated keywords in your seven keyword slots (“libros bilingües para niños” alongside “bilingual books for kids”), a description naming both languages in the first two lines, and the translated title worked into the subtitle so it surfaces in search. Readers search in their own language; English-only metadata hides you from half your audience.

Choose categories with both markets in mind — a Spanish-English children’s book might sit in Children’s Foreign Language Books plus the relevant age-range categories.

If you publish split editions instead — one edition per language — each needs its own ISBN, cover, and listing. Never reuse one ISBN across two products. And if you publish wide through IngramSpark as well as KDP, use the same ISBN for the same edition on both platforms rather than taking a free ISBN from each: one edition, one number, everywhere.

The 8-Point Bilingual Formatting Checklist

Run through this list before you export your final files. Every item is a real mistake that has sunk real bilingual books.

• Both languages proofread independently by native speakers — a translator is not a proofreader, and errors hide in the language you read least carefully.
• Paragraph alignment verified across the whole book — every translated paragraph sits opposite or directly after its match, with no orphans or drift.
• Font coverage checked for every character — search the PDF for tofu boxes; test accented capitals, punctuation, and numerals in both scripts.
• Both scripts set at visually matching sizes — non-Latin text often needs an extra half to full point plus generous leading.
• RTL paragraphs explicitly set to right-to-left direction — never faked with alignment; punctuation verified at both ends of sentences.
• All fonts embedded and subset in the print PDF — confirmed in the PDF reader’s font list, not assumed from export settings.
• Facing pages consistent throughout — language A always on the same side, chapters breaking together, padding pages where needed.
• Metadata bilingual — both languages in keywords, description, and subtitle; categories checked against competing titles. For illustrated books, our eBook image formatting guide covers the specs that keep dual-language illustrations crisp.

Frequently Asked Questions

Should I put both languages on the same page or on facing pages?

Use facing pages for print books where comparison matters — literary translations, language learning, poetry. Use interleaved paragraphs for reflowable eBooks, where facing pages are impossible. Use side-by-side columns only in wide fixed layouts.

Can I use the same font for both languages?

Yes — one family with broad script coverage, such as Google’s Noto family, keeps both languages visually unified and avoids missing-glyph errors. Verify it contains every character you need, and adjust size and leading so both scripts carry equal weight.

How do I format an English-Arabic (or other right-to-left) book?

Set RTL paragraphs to right-to-left direction explicitly (paragraph direction in Word, dir=“rtl” in EPUB). Build the print PDF to open right-to-left, and state the reading direction in your book description.

Is a bilingual book more expensive to print?

Usually, yes. Facing-page layouts roughly double the page count, which raises the print cost per copy. Factor this into your list price before finalizing the layout — or use interleaved paragraphs to keep the page count down.

Should I publish one bilingual book or two separate editions?

One bilingual book when readers want to compare the languages — children’s books, language learning, heritage titles. Two separate editions when one language’s market dwarfs the other; each edition needs its own ISBN and listing.

What language do I set in KDP metadata for a bilingual book?

Set the primary Language field to your main audience’s language, then make the rest bilingual: keywords in both languages, a description naming both languages up front, and the translated title in the subtitle so it surfaces in search.

Conclusion: Two Languages, One Clean Book

Bilingual book formatting is a discipline of pairs: two languages, two scripts, two sets of readers — held together by consistent choices. Pick one layout and commit, set both languages in a font that truly covers them, align every paragraph with its translation, embed your fonts, and make your metadata speak both languages. Do that, and your dual-language book will feel like one confident product — the kind bilingual families buy, teachers recommend, and language learners finish.