Upwork proposal templates for translators

Clients hiring a translator on Upwork usually screen for four things first: your exact language pair, your subject-matter experience, proof that you can preserve meaning and tone, and whether you noticed the details in the job post.

Template 1: Short document translation

Hi {{client_name}}, I read that you need {{word_count}} words translated from {{source_language}} to {{target_language}} for {{document_type}} by {{deadline}}. I can help with that.

I translate {{source_language}} to {{target_language_variant}} with a focus on natural phrasing, not word-for-word output. For this document, I’d keep the tone {{tone_goal}} and make sure terms like {{specific_term_1}} and {{specific_term_2}} are handled consistently.

Relevant experience:
- {{years_or_background}} translating {{industry_or_topic}} content
- Similar work: {{sample_description}}, available in my portfolio or as a short excerpt
- Comfortable working in {{file_format}}, and I can return the translation with {{formatting_requirement}}

My process would be:
1. Review the full file and confirm any terms that need a fixed translation.
2. Translate the document in {{tool_or_format}}.
3. Do a separate proofreading pass for accuracy, tone, names, numbers, and formatting.

One quick question: should the translation sound more {{tone_option_1}} or {{tone_option_2}} for your readers?

If the file is ready, I can start {{start_time}} and deliver by {{delivery_time}}.

Best,
{{your_name}}

Template 2: Website or app localization

Hi {{client_name}}, I noticed you’re localizing {{website_or_app_name}} from {{source_language}} into {{target_language_variant}}, especially the {{specific_pages_or_sections}}. That needs more than direct translation because the copy has to sound natural to {{target_audience}}.

I can translate and localize the content so it keeps the original meaning while fitting local wording, tone, and calls to action. I’ll pay close attention to UI limits, button labels, repeated terms, and any brand phrases you want kept consistent.

Relevant background:
- I’ve translated {{type_of_content}} for {{industry_or_user_type}}
- I can work from {{source_format}}, including {{strings_spreadsheet_CMS_JSON_or_docs}}
- I can provide a terminology list for repeated words like {{example_term_1}}, {{example_term_2}}, and {{example_term_3}}

For your project, I’d suggest this workflow:
1. Confirm the target variant: {{target_language_variant}}, not just {{general_language_name}}.
2. Translate the strings/pages in your preferred format.
3. Flag anything that needs context, such as short buttons, error messages, or unclear placeholders.
4. Do a final pass for consistency across navigation, forms, and calls to action.

A couple of questions before I estimate the final timeline: Do you want a formal or conversational tone? And will I see screenshots or page context for short UI strings?

I’m available {{availability}} and can start with {{first_milestone_or_sample_section}} if useful.

Best,
{{your_name}}

Template 3: Specialized or sensitive translation

Hi {{client_name}}, I read that this is a {{legal_medical_financial_technical_or_academic}} translation from {{source_language}} to {{target_language_variant}}, and that accuracy around {{specific_topic_or_terms}} is important. I’m a good fit because {{specific_relevant_background}}.

For this type of translation, I don’t rely on a rough literal pass. I check terminology, numbers, dates, names, units, and any phrases that could change meaning if translated too directly. If a sentence is ambiguous, I’ll flag it instead of guessing.

Relevant proof I can share:
- {{sample_or_portfolio_item}} related to {{topic}}
- {{credential_or_domain_experience}}, if relevant
- A short paid or unpaid excerpt from your file, if you want to confirm style before starting

My process:
1. Review the source file and confirm the target audience: {{audience}}.
2. Build or follow your glossary for terms such as {{term_1}}, {{term_2}}, and {{term_3}}.
3. Translate in {{format_or_tool}} while preserving {{formatting_or_structure}}.
4. Proofread separately against the source text before delivery.

One important note: if you require a certified, sworn, or notarized translation, please confirm the exact requirement. {{certification_status_sentence}}

If that matches what you need, I can deliver {{deliverable}} by {{deadline}}.

Best,
{{your_name}}

What clients hiring translators screen for first

Start with a line that proves you read the post

A translator proposal should not start with “I am a professional translator with many years of experience.” That could be sent to any job. Your first line should mention the client’s file, language direction, audience, deadline, or content type.

• Weak: “I can translate this for you quickly and accurately.”
• Better: “I saw you need a 2,000-word product manual translated from English to Brazilian Portuguese while keeping the tables and safety warnings intact.”
• Weak: “I have experience in website translation.”
• Better: “I noticed your checkout and onboarding pages need to sound natural for Mexican Spanish users, not just translated line by line.”
• Weak: “I can do legal translation.”
• Better: “I read that these are employment contract sections, so I’d pay close attention to defined terms, dates, names, and jurisdiction-specific wording.”

What to customize before sending

1. 1

   Name the language direction

   Say the source and target language clearly. Include the variant when it matters: Canadian French, European Portuguese, US English, Latin American Spanish, Simplified Chinese, or Traditional Chinese.

2. 2

   Match the client’s content type

   A proposal for subtitles should mention timestamps, character limits, and reading speed. A proposal for contracts should mention defined terms and consistency. A proposal for ecommerce should mention product names, size charts, and calls to action.

3. 3

   Mention the file format

   Clients care whether you can work in Word, PDF, Excel, Google Docs, subtitle files, CMS exports, JSON, or design files. If the format affects time or quality, say so.

4. 4

   Ask one useful question

   Ask about tone, target market, glossary, context, or certification requirements. Do not ask a question already answered in the post.

5. 5

   Adjust the proof

   Use the proof that matches the job. For a medical leaflet, show healthcare translation experience. For app strings, show UI localization work. For literary translation, show style and voice.

Proof to include and how to link it

Translator proof works best when the client can judge accuracy, tone, and fit quickly. Do not send a huge folder and expect them to search. Point to one or two relevant samples and explain why they matter.

• Add a side-by-side excerpt: source text on the left, your translation on the right, plus one sentence about the audience and tone.
• For confidential work, create a redacted sample or a short mock sample in the same domain.
• For website or app localization, show screenshots or a spreadsheet sample with context notes.
• For subtitles, include a short clip excerpt or subtitle file sample and mention timing, line breaks, and readability.
• For technical translation, include a small glossary sample to show term consistency.
• If you have credentials, name them plainly. Do not imply certification, sworn status, or legal authority you do not have.
• If the client asks screening questions, answer each one directly instead of pasting the same cover letter again.

Mistakes that get translator proposals skipped

• Claiming too many languages. “I translate 20 languages” can make clients worry that you are reselling or using machine output without review.
• Ignoring the language variant. Spanish for Spain, Mexico, and Argentina are not the same buying experience. The same applies to many other languages.
• Not mentioning the source file. A PDF scan, subtitle file, spreadsheet, or CMS export changes the work.
• Promising perfect translation with no questions. Serious clients know context matters.
• Using a generic opening. If the first line could fit any translation job, rewrite it.
• Hiding machine translation use. If your workflow includes MT post-editing, say so when relevant and explain your human review process.
• Sending unrelated samples. A poem does not prove you can translate a privacy policy. A contract does not prove you can localize app onboarding copy.
• Skipping confidentiality. For legal, medical, HR, finance, and internal business documents, clients want care with private material.
• Overpromising certification. Certified, sworn, notarized, and official translations can mean different things depending on the client’s country and use case.

A simple translator proposal structure

1. 1

   Line 1: prove you read it

   Mention the language pair, content type, and one detail from the post.

2. 2

   Line 2: state the fit

   Connect your experience to the exact topic, audience, or file type.

3. 3

   Middle: show your process

   Explain how you handle terminology, formatting, proofreading, and questions.

4. 4

   Proof: link one relevant sample

   Point to the sample and explain what it proves. Do not attach everything.

5. 5

   Close: ask one next-step question

   Ask about tone, glossary, context, certification, or delivery format.

If you want help choosing which translator jobs are worth your Connects, BidGrow can score new Upwork jobs using rules you can read, including payment verification, client spend, hire rate, rating, activity, competition, Connects cost, and rate fit. It can also draft proposals from your own templates, but you always review and send them yourself. BidGrow is not affiliated with or endorsed by Upwork.