Should you translate your own book? When it works and when it doesn't
You can translate your own book, but it works less well than most authors expect. If you speak the target language well, you can write correct sentences in it. That isn't the same as writing a book a local reader will forget was translated. Most people who try find this out halfway through, after months of work.
That doesn't mean you shouldn't try. It means it's worth knowing in advance what's waiting for you, and where you're most useful in the process.
Why it looks like a good idea
Because there's logic to it. Nobody knows the book like you do. You know why the character said that line, what the joke in chapter three is, and which hint you planted at the start that pays off at the end.
A translator, however good, has to guess some of these things. You don't.
And there's the matter of freedom. A translator is bound to the original. You can decide that a certain joke doesn't work in the English version and write a different one in its place. You can shorten a chapter that now feels too long to you. It's your book.
What authors find out halfway through
That they're rewriting, not translating. The moment you meet your text again, you see things in it you'd like to change. Every page becomes a chance to improve, and the translation takes several times longer.
That the second language sounds like a second language. Even for people who have lived in that language for years. The sentences are correct, but their structure is Hebrew. The word order, the sentence length, how characters address each other in dialogue. A local reader feels it even if they can't explain what's bothering them. We wrote about this in why dialogue in a translated book sounds a little stiff.
That it's hard to see your own text from the outside. When you read the translation, you hear the original in your head. A sentence that's unclear to a foreign reader sounds perfectly clear to you, because you know what it's supposed to say.
That it takes a lot of time. Translating a whole book is months of work, even for professional translators. For an author doing it in the evenings, it can be a year. And that's a year in which they're not writing the next book.
When it does work to translate your own book
For some authors it works nicely.
When the second language is almost a first language. Someone who grew up in a bilingual home, or who has lived and written in the second language for years, can write in it with a natural voice.
When the book is short. A children's book, a short poetry collection or a short nonfiction booklet is a project you can finish without losing your mind.
When you want a free version. If the goal isn't a faithful translation but a new version of the book for a different audience, you really are the right person to write it.
The middle path
Many authors find that their best role isn't writing the translation but checking it.
It looks like this. Someone else prepares a draft: a human translator, or an AI-based translation tool. You go over it, marking where the intention got lost, where a joke fell flat, where a character doesn't sound like themselves. And at the end a native speaker reads the text and makes sure it sounds natural.
That way you contribute what only you know, without spending months writing every sentence from scratch.
| Path | The advantage | What to watch for |
|---|---|---|
| You translate alone | Full control over your intentions | A lot of time, and the text may not sound natural |
| A translator or tool drafts and you check | Keeps your intentions and saves time | You need to know what to look for when checking |
| A professional translator alone | Natural text in the target language | You need to brief them well on the book |
How to test whether it suits you
Translate one chapter. Not the first one, which has already been edited endlessly, but a chapter from the middle.
Note how long it took, then multiply by the number of chapters. Give the chapter to a native speaker who doesn't know the book, and ask them just one question: does this sound like a book written in your language?
If the answer is yes and the time is reasonable, you have your answer. If not, that's an answer too, and it saved you months. On how to tell a translator what your book should sound like, we wrote how to tell a translator how the book should sound.
Frequently asked questions
My English is good. Is that enough to translate my book?
Usually not. Speaking a language and writing a book in it that sounds natural to a local reader are two different skills. Most people write correctly in their second language, but not in a way that sounds like a book written in it.
What's the advantage of translating yourself?
You know exactly what you meant to say. There's no risk of a translator missing an intention, an irony or a hint you planted. And you're free to change the original, because it's yours.
What's the big downside?
Time. Translating a whole book is months of work, and most authors discover they're rewriting instead of translating. And even after all that, the text needs a read by a native speaker.
Is there a middle path?
Yes. You can have someone else, a person or a tool, prepare a draft, and then go over it yourself. That way you keep your intentions without writing every sentence from scratch. At the end it's still worth having a native speaker read it.