For authors & literary translators
Translate a book without losing the voice
A character glossary that holds across 300 pages. A styleguide built from a sample chapter. Sentence-level alternatives for dialogue. A polish pass that respects literary rhythm. The workflow indie authors and literary translators have been waiting for.
Free to begin · No card required
Books are where AI translation breaks most visibly. By page 30 the protagonist has three names; by page 60 the dialogue voice has flattened; by the end of the manuscript, the recurring metaphor has shifted into something the author wouldn’t recognize. For literary translators, indie authors, and small publishers, this is the gap between "AI can translate" and "AI can produce a publishable manuscript". This workflow closes it: a character glossary that holds across 300 pages, a styleguide built from a sample chapter, sentence-level alternatives for dialogue, Pro-mode translation for the prose, and a polish pass that respects literary rhythm. The output is a manuscript an editor can read — not a draft that has to be rewritten.
How does a literary translator work here?
Books are where generic translation tools fail most visibly — by page 30 the protagonist has three names, the dialogue voice has flattened, and the recurring metaphor has shifted. This workflow is built to hold all of that.
Import the chapter
Upload DOCX or paste the chapter. Or pull from Scrivener’s Markdown export. The chapter becomes editable blocks with the original structure intact.
Build the character glossary
Add character names, place names, recurring objects, invented words. Pin each to a target-language rendering. The glossary travels with every chapter — page 1 to page 500.
Build the styleguide from a sample
Paste in the opening pages translated by hand, or by an editor you trust. Transept reads them and proposes a styleguide — sentence rhythm, register, dialogue tone — that captures the voice. Refine, save, reuse across chapters.
Translate, with alternatives where dialogue lives
Pro mode for the prose. For dialogue, walk through the alternatives view — three to five renderings per line, picking the one that sounds like the character.
Polish for literary rhythm
A polish pass smoothes the rhythm without touching the choices you made. Read it through. Make the last manual edits.
Export to DOCX or Markdown
For your editor, your typesetter, or your KDP upload. Formatting intact, footnotes preserved, chapter breaks where they belong.
Why are books different?
The glossary holds the world
Character names, place names, invented vocabulary — the fabric of the story. Pinned once, reused for every chapter, every translator, every edition.
The styleguide holds the voice
Dialogue rhythm, narrative register, how to handle humor and idiom — the things that distinguish "translated" from "well-translated".
Pro mode for the prose
Standard works for marketing copy. For literary work, Pro’s deeper models catch the nuance that determines whether the translation is publishable.
8 hours → 50 minutes
One 40,000-word document, translated by several agents at once, used to take eight hours. We got the agents to sync their memory mid-run, so a term settled in chapter 2 still holds in chapter 40. It now finishes in fifty minutes.
How the syncing works— Don’t take our word for it —
The editor, in miniature
A working slice of the real thing — Literess, glossary, styleguide, workflows, and the translation memory are all live. Click around.

Here to help you translate
A key turned in the lock and the door swung open.
У замку повернувся ключ, і двері розчахнулися.
The knock came just before midnight.
Стукіт пролунав перед самою північчю.
FAQ
- Yes — chapter by chapter, or batched. A 90,000-word novel in Pro mode runs about 270K words — comfortably inside a few months of the Starter plan, or a top-up pack.
- Dialogue tags ("she said", "he murmured") translate naturally. Stage directions and beats stay as prose. The styleguide can include rules for how to handle each.
- Add them as comments on the translated sentence. They stay in the workspace; they don’t show up in the exported manuscript.
- Yes — team review supports two translators on the same document with sentence-level locking. Or use client review links for a beta reader’s pass.
- The main types of literary translation — novels and short fiction, narrative non-fiction and memoir, children’s and YA, and genre work (sci-fi, fantasy, romance, thriller) — all fit the workflow, because they share the same hard problems: a cast of names that must stay consistent, a narrative voice that has to survive the trip, and dialogue that has to sound like the character. Poetry and tightly metered verse are the exception: AI is a starting point there, and the human craft still carries most of the weight.
- Neither — Transept is software you use to do the translation yourself. If you’re comparing literary translation services and companies, the difference is that you keep control of the voice and the choices (and the margin) instead of handing the manuscript off. Many freelance literary translators use Transept as their first-draft and consistency layer, then sell their human review as the service.
- Yes — indie authors translating their own books, small literary publishers translating acquisitions, and freelance literary translators using AI as the first-draft layer. The output is meant to be reviewed and refined by a human, not shipped as-is — but it cuts the first-draft time by 70–80%.
- Partial. For prose with rhythm and rhetorical figures, Pro mode plus a careful styleguide usually preserves the feel. For metered verse and tight rhyme schemes, AI translation is currently a starting point — significant human craft is still required.
- Transept supports the languages its frontier models handle. For minor European languages and many Asian languages, quality is strong. For very rare or extinct languages, the major models are limited and human translation remains the better path.
- Add them as comments on the translated sentence (visible only in the workspace) or as footnotes that export with the document (visible to the reader). Both are supported.
- Yes — team review supports two translators on the same manuscript with sentence-level locking, real-time presence, and shared glossary/styleguide. Common pattern: one translator does the first pass, one does the literary review.
Keep reading around this workflow
- FeatureA styleguide that steers every regeneration→Tone, register, rules, formatting conventions. Build a styleguide manually or have Transept generate one from a sample page of finished…
- FeatureA glossary the AI actually follows→Character names, product terms, branded phrases, client-specific vocabulary. Build a glossary once — manually, by upload, or seeded from a…
- Use caseTranslate the next post without losing your voice→Long-form content lives or dies on voice. Run your post through Transept with a styleguide built from your own writing, choose from…
Translate the chapter and have it still sound like the book
Start translatingFree to begin · No card required

