How to Translate a Resume or CV to English Without Losing the Formatting
How to translate a resume to English without wrecking the layout: which file to start from, what to leave alone, and how to check the result before you apply.
Every few weeks someone asks us the same thing in slightly different words. They need to translate a resume to English for a job application abroad, they have a two-page Word file with a photo, a sidebar of skill bars and a couple of invisible tables holding the whole thing together, and they want it to look the same afterwards. The translation itself is rarely the hard part. A CV is short, the vocabulary is narrow, and current AI models handle it well. The layout is what falls apart, and it usually falls apart in ways the applicant does not notice until a recruiter opens the file.
Here is what we have learned from watching people do this badly and then doing it properly.
What actually breaks when you translate a CV
Three things go wrong, and they go wrong in a predictable order.
The first is text that never gets translated at all. Resume templates are full of containers that are not ordinary paragraphs: text boxes, shapes with labels inside them, sidebars built as a single-cell table, contact details sitting in the header. Some tools read the main body and skip the rest. We have seen a finished CV where the summary and work history were in fluent English and the entire left column, the one with the job titles, was still in Russian. The applicant sent it to four companies before anyone told them.
The second is text that no longer fits. English is not uniformly shorter or longer than other languages, but individual lines move a lot. A German job title that fit one line becomes two. A French bullet point that fit one line becomes two and pushes the last entry onto a third page, which for a CV is worse than a typo. Tight templates, the ones designed to fill exactly one page, have no slack anywhere.
The third is structure that survives visually but breaks for machines. A lot of applications go through an applicant tracking system before a person sees them. Those systems pull the text stream out of a DOCX. Content inside text boxes, headers and footers, and multi-column tables often comes out in the wrong order or does not come out at all. A CV can look perfect in Word and arrive as a scrambled paragraph on the recruiter's screen. Translation does not cause this, but it is the moment you are most likely to introduce it, because the temptation is to fix overflow by moving things into a box.
Start from the file the CV was written in, not the PDF
The single biggest predictor of how much manual work you will do is which file you start from. An editable DOCX keeps its styles, tab stops and table structure, and the translated text lands back in the same places. A PDF does not carry any of that. Converting one gives you a document that looks similar and behaves nothing like the original: text frames instead of paragraphs, line breaks baked in where the line happened to end, fonts substituted, spacing hardcoded.
We watched a designer's CV go through this. It had been built in Canva, exported as a PDF, and the editable version was gone. Translating the PDF produced a file that looked right at 100% zoom and collapsed the moment anyone edited a line. Rebuilding it in Word took about two hours, most of it spent matching a sidebar that turned out to be a background image with text on top. The second time that person needed a language version, they asked their designer for the source file first.
So before anything else, find the original. Ask whoever made it. Check whether the CV started life in Google Docs, in which case download it as DOCX rather than exporting a PDF, then confirm the download still looks right. If the only copy that exists is a PDF, accept that you are doing layout work either way and decide whether to rebuild it in a plain template you can reuse. Our view is that rebuilding is usually the better trade, because you will need this document again in six months.
There is one case where a PDF is fine: a scanned or photographed diploma or reference letter that you are attaching alongside the CV. Those are evidence documents, not living files, and a translation delivered as a separate readable page is normal. We have written more about the practical differences between DOCX and PDF as translation sources if you want the longer version of this argument.
How to translate a resume to english without rebuilding the layout
The workflow that works is boring and has four steps.
Get the editable file. Clean it up before translating, not after: delete the empty paragraphs people leave behind, turn any decorative text box that holds real content into a normal paragraph or a proper table cell, and remove the photo temporarily if it is anchored somewhere strange. Ten minutes here saves an hour later.
Translate the whole file, not visible sections. Whatever you use, check afterwards that headers, footers, text boxes and table cells all came through. The fastest test is to search the finished document for a common word in the source language. If you find hits, something was skipped.
Fix the language of the document, not just the words. Word stores a language setting per run of text, and translated files often keep the original one, which means the spellchecker underlines correct English and a recruiter who clicks into the text sees red everywhere. Select everything, set the proofing language to the target English variant, then run the spellchecker properly.
Then do the layout pass with fresh eyes, on a printed page or a PDF export rather than in the editing view. Check page count first, then line breaks inside job titles, then anything that wrapped where it did not wrap before.
This works best when the CV is a single well-behaved DOCX. It does not apply cleanly to CVs built as InDesign or Figma layouts, academic CVs running to fifteen pages with publication lists, or anything where the design is the point, such as a portfolio-style resume for a creative role. Those need a designer in the loop, and pretending otherwise wastes a day. Our general guide on translating a DOCX without breaking the layout covers the mechanics in more depth for longer documents.
The parts of a CV you should not translate literally
This is where AI translation and inexperienced human translators make the same mistakes, and where the damage is real, because a recruiter reads a job title and a degree in about two seconds.
Job titles need judgment rather than translation. A Russian "инженер-конструктор" comes back from most tools as "constructor engineer", which means nothing to a British hiring manager. The functional equivalent is design engineer. We have seen "главный специалист" rendered as "chief specialist", a title that sounds senior in the original and vaguely made up in English. If the target market has a recognised name for the role, use that, and if it does not, describe the role plainly rather than inventing a compound noun.
Employers, universities and institutions keep their legal names. Do not translate a company name unless it has an official English form the company itself uses. The usual pattern is the original name, then a short explanation in brackets the first time it appears, such as the industry or the city.
Degrees are the trickiest item on a CV, because equivalence is a legal question and not a linguistic one. A Russian or Kazakh "специалист", a German Diplom-Ingenieur and a French Licence do not map onto Bachelor or Master cleanly, and claiming an equivalence you have not had assessed is a risk you do not need to take on a CV. Give the degree as awarded, add the field and the year, and let the employer or the credential evaluator do the conversion. If an institution requires a formal equivalence statement, that is a certified translation plus a recognition procedure, which is separate work from your CV.
Dates, addresses and phone numbers need reformatting rather than translating. Write months as words or use an unambiguous order so 09/04 cannot be read two ways, put the phone number in international format, and swap the address into the order the target country expects.
Two-column templates, text boxes, and the other quiet troublemakers
Most CV formatting problems trace back to one of a handful of template patterns, and knowing them tells you where to look.
Two-column layouts built with a table are the most common. They usually survive translation well, because table cells hold their position, but they do change row heights when the text inside grows, which shifts everything below. Two-column layouts built with actual Word columns behave worse: text reflows across the column break, so a slightly longer sentence in the left column pushes your education section over to the right. If you have a choice, table-based sidebars are safer.
Text boxes and shapes look convenient and cause the most trouble. They do not grow with their content, so longer translated text either overflows invisibly or gets clipped. Word will not warn you. The only reliable check is to look at every box after translation. If a template uses boxes for the whole sidebar, consider moving that content into a table before you translate anything.
Skill bars, rating dots and icon rows are graphics with labels. The labels are text and get translated; the graphics are meaningless to an ATS and often to the recruiter. We generally suggest replacing them with a plain line of text, which reads better in English-language markets anyway, where self-assigned proficiency percentages are unusual.
Fonts are the last one. A template built around a font that has no Cyrillic, Greek or Vietnamese coverage will silently substitute another font for those characters, and going the other direction, a document originally set in a font with a narrow Latin set can shift metrics enough to change line breaks. Check that the font you end up with actually contains every character in the finished file, and if you are unsure, move to something with broad coverage before you start.
Checking the translated CV before you send it
A CV is short enough that you can check it properly, which is not true of most documents, so do it.
Read the English version on its own, without the source next to you. If a sentence would make a native speaker pause, fix it, even if it is an accurate rendering. Recruiters read CVs fast and charitably, but not that charitably.
Then compare against the source for the things that carry factual risk: dates of employment, dates of study, company names, the degree, the certification numbers, and anything numeric in an achievement line. AI translation rarely mangles a name and occasionally mangles a number, so numbers are where a second pass earns its time. A percentage that becomes a different percentage in a bullet about revenue growth is the kind of error that ends an application if someone checks.
Export to PDF and look at the PDF, because that is what the recruiter opens. Count pages. Look for a heading stranded at the bottom of a page, a bullet that wrapped to a single orphaned word, and anything clipped at the edge of a box. Then copy all the text out of the PDF and paste it into a plain text editor. The order you get is roughly the order an automated parser will see, and if your job titles come out after your hobbies, you know the structure needs work.
If you translate documents like this often enough that the manual steps get old, SnapIntel handles the mechanical part: you upload the DOCX, review and approve the glossary and the instructions before translation starts, and get back a translated DOCX in the same structure plus a QA report flagging what it is unsure about. The trial covers 5,000 words over seven days without a card, which is more than enough for a CV and a cover letter. The judgment calls in the section above are still yours, and they should be.
What we would do with a CV due tomorrow
Find the DOCX. If there is only a PDF, decide in the first five minutes whether you are rebuilding it or accepting a rough layout, and do not spend an hour discovering that by accident.
Flatten the traps before translating: text boxes into paragraphs or table cells, empty paragraphs deleted, photo anchoring checked.
Translate everything, then search the result for a source-language word to prove nothing was skipped.
Set the proofing language and run the spellchecker.
Handle the four judgment items by hand: job titles, institution names, the degree, and date and phone formats.
Export to PDF, read it as a stranger would, count the pages, and copy the text out to see what a parser sees.
That is about forty minutes of work for a one-page CV if the source file is clean, and most of it is not translation at all. Worth knowing before you promise someone a language version by morning.