Per-Word vs Per-Hour Pricing for Translators: Which Is Better?

Every freelance translator faces the pricing-structure question early in their career: should I charge per word, per hour, per project, or per line? The instinct is to pick one and stick with it — usually per word, because it is what most agencies and direct clients expect — but the right answer is rarely that simple. Different pricing structures serve different types of work, different types of clients, and different types of translators. A translator who charges per word for everything is leaving money on the table for editing and proofreading work, where per-hour pricing produces 30-50% higher effective earnings. A translator who charges per hour for everything is losing clients who want predictable project costs and losing income on repetitive content where per-word with CAT tool leverage produces higher earnings.

This guide walks through the four main pricing structures freelance translators use — per word, per hour, per project, and per line — and helps you choose the right one for each type of work. We will cover the advantages and disadvantages of each structure, the per-word advantages (transparent, scalable, industry standard) and per-hour advantages (fair for slow texts, appropriate for editing work), the per-project structure (best for fixed scope and value-based pricing), the per-line structure (a European tradition that is rare in English-speaking markets), the minimum fee that protects you from unprofitable small jobs, and the rush surcharge that protects you from disruptive deadlines. The framework here is the same one used by working freelance translators and translation agency project managers.

By the end, you will have a clear framework for choosing the right pricing structure for each project, and a defensible rate for each structure that produces consistent effective hourly earnings across your client base. If you want to skip ahead and run the numbers for your own situation, the freelance translator rate calculator implements the exact framework described below.

Why the Pricing Structure Question Matters More Than the Rate Itself

The pricing structure question — per word, per hour, per project, or per line — matters more than the rate itself because the structure determines how the rate interacts with the work. A translator charging $0.15 per word on a 3,000-word document earns $450, whether the document takes 5 hours or 15 hours to translate. The same translator charging $50 per hour on the same document earns $250 if it takes 5 hours and $750 if it takes 15 hours. The rate is the same ($90 effective hourly at $0.15 per word × 600 words per hour); the structure determines whether the translator benefits from efficiency (per word) or is protected from difficulty (per hour).

The pricing structure also affects which clients the translator can serve. Agencies almost universally price per word, because they need to quote clients a fixed project cost before the work begins, and per-word pricing produces that fixed cost from the word count alone. Direct clients are more flexible — many will accept per-project pricing for fixed-scope work, and some will accept per-hour pricing for ongoing editing and review work. A translator who only offers one pricing structure is limiting their client base to the clients who prefer that structure.

The third reason the structure question matters is that it determines which kinds of work the translator can profitably accept. Translation work is well-suited to per-word pricing because the word count is measurable and the per-word rate produces a predictable project cost. Editing and proofreading work is poorly suited to per-word pricing because the throughput varies dramatically (a clean document might take 1,500 words per hour; a poorly written document might take 400 words per hour), and per-word pricing penalizes the translator for the difficulty of the source text. Project management, consulting, and advisory work is poorly suited to per-word pricing because the deliverable is not a word count — and per-hour or per-project pricing is the only structure that captures the value.

Per-Word Pricing: The Industry Standard

Per-word pricing is the industry standard for translation work, and for good reason. The structure is transparent (the client knows the cost before the work begins), scalable (the rate applies to any size project), and rewards efficiency (the translator benefits from faster translation, not from slower translation). The structure works because translation work has a measurable, comparable unit (the source word) that determines the project cost.

Advantages of per-word pricing

• Transparency: The client can calculate the project cost from the word count alone, before the work begins. No surprises, no scope disputes.
• Scalability: The same per-word rate applies to a 100-word email and a 100,000-word manual. The structure does not need to be renegotiated for each project.
• Rewards efficiency: A translator who improves their throughput (through CAT tools, specialization, or experience) earns more per hour without raising the per-word rate. The incentive is to translate faster and better, not slower.
• Industry standard: Agencies expect per-word pricing; direct clients are familiar with it. The structure does not require client education.
• Compatible with CAT tool leverage: Translation memory discounts (fuzzy match, exact match) are applied to the per-word rate, allowing the translator and client to share the productivity benefit.

Disadvantages of per-word pricing

• Penalizes difficulty: A poorly written source text takes longer to translate than a well-written one, but the per-word rate is the same. The translator absorbs the cost of source-text difficulty.
• Penalizes creative content: Marketing transcreation, where the translator is rewriting rather than translating, takes longer per word than literal translation. Per-word pricing underprices creative work.
• Incompatible with editing and proofreading: The throughput on editing and proofreading varies too dramatically (400-2,000 words per hour depending on source quality) for per-word pricing to produce fair compensation.
• Commoditizes the work: Per-word pricing makes it easy for clients to compare translators on rate alone, without considering quality, specialization, or reliability. This is the structure's biggest weakness in the agency market.

The default for most translation work should be per-word pricing. The structure works for the vast majority of projects, and the disadvantages can be mitigated with the right rate card (higher per-word rates for creative content, minimum fees for small projects, rush surcharges for tight deadlines).

Per-Hour Pricing: Fair for Editing, Proofreading, and Difficult Texts

Per-hour pricing is the right structure for work where the throughput varies dramatically and the per-word rate cannot fairly compensate the translator for that variance. The most common applications are editing and proofreading (where the source quality determines throughput), project management (where the deliverable is not a word count), and translation of poorly written source texts (where the per-word rate would underprice the difficulty).

Advantages of per-hour pricing

• Fair for variable-throughput work: Editing and proofreading throughput varies from 400 to 2,000 words per hour depending on source quality. Per-hour pricing compensates the translator for the actual time, regardless of source quality.
• Appropriate for non-translation work: Project management, consulting, terminology research, and client communication are all billable per hour but not per word.
• Protects against scope creep: A project that expands beyond the original scope (additional revision rounds, additional file formats, additional client consultation) is automatically compensated at the hourly rate.
• Transparent about time: The client sees exactly how much time the work is taking, which builds trust and justifies rate increases.

Disadvantages of per-hour pricing

• Penalizes efficiency: A translator who works faster earns less. The incentive is to work slower, which is bad for both the translator (lower effective hourly if they slow down intentionally) and the client (slower delivery).
• Unpredictable project cost: The client does not know the total cost until the work is complete. Many corporate clients require fixed project costs for budget approval and will not accept per-hour pricing for translation work.
• Requires time tracking: The translator must track time accurately, which adds administrative overhead and creates potential disputes over billable hours.
• Incompatible with most agency work: Agencies need fixed project costs to quote their clients. Per-hour pricing is rarely accepted for translation work by agencies, though it is accepted for editing and proofreading.

Per-Project Pricing: Best for Fixed Scope and Value-Based Work

Per-project pricing is the structure where the translator quotes a flat fee for the entire project, regardless of word count or hours. The structure is best for fixed-scope work where the deliverable is well-defined, and it is the gateway to value-based pricing — quoting a project fee based on the value delivered rather than the time or words.

Advantages of per-project pricing

• Predictable project cost: The client knows the cost upfront, which is essential for corporate budget approval and for client trust.
• Rewards efficiency: The translator benefits from faster delivery, just as with per-word pricing.
• Enables value-based pricing: A translator who writes a 500-word sales page that generates $200,000 in client revenue can quote $5,000 for the project, regardless of whether it took 5 hours or 50 hours. The fee reflects the value, not the time.
• Appropriate for non-translation deliverables: Project management, transcreation campaigns, and consulting engagements are best priced per-project.
• Differentiates from agency commodity pricing: Direct clients who pay per-project are paying for the outcome, not the input — and they are typically higher-quality clients than those who shop per-word rates.

Disadvantages of per-project pricing

• Requires accurate scoping: The translator must accurately estimate the project scope before quoting, or risk underpricing. A 5,000-word document quoted at $750 ($0.15 per word) that turns out to be 8,000 words is a $450 loss.
• Risk of scope creep: The client may add scope (additional revision rounds, additional file formats, additional consultation) without accepting a price increase. The contract must define scope explicitly.
• Incompatible with agency work: Agencies need per-word pricing to maintain consistent margins across their translator pool. Per-project pricing is rarely accepted by agencies.
• Requires more sales skill: Per-project pricing requires the translator to defend the project fee against client pushback, which is a different skill than defending a per-word rate.

Per-project pricing is the structure most strongly correlated with high freelance translator earnings. ATA compensation surveys consistently show that translators who quote per-project to direct clients earn 40-80% more per hour than translators who quote per-word to the same clients, because per-project pricing enables value-based pricing on work where the value exceeds the time or word count.

Per-Line Pricing: The European Tradition

Per-line pricing is a structure used primarily in European markets, particularly in Germany, Austria, Switzerland, and parts of France. The standard line is defined as 55 characters (including spaces) of target text, and rates are quoted per line rather than per word. The structure was developed in the pre-CAT-tool era as a way to standardize pricing across languages where word counts vary dramatically (a 1,000-word English document might be 850 words in German or 1,150 words in Spanish, but the character count is more stable).

Converting per-line to per-word

The conversion between per-line and per-word rates depends on the average word length in the target language. For English, the average word length (including the trailing space) is roughly 5.5 characters, so a 55-character line averages 10 words. A per-line rate of $1.50 is roughly equivalent to a per-word rate of $0.15. For German, the average word length is closer to 6.5 characters, so a 55-character line averages 8.5 words; a per-line rate of $1.50 is roughly equivalent to a per-word rate of $0.18.

Per-word equivalent = Per-line rate ÷ Average words per line
Average words per line (English) ≈ 10 (55 characters ÷ 5.5 characters per word)
Average words per line (German) ≈ 8.5 (55 characters ÷ 6.5 characters per word)

Example: $1.50 per line in English ≈ $0.15 per word
Example: $1.50 per line in German ≈ $0.18 per word

Per-line pricing is rarely seen in English-speaking markets, but it is useful for translators working with European agency clients who expect the structure. The rate equivalent should be calculated carefully, because the per-line rate that sounds low can produce a per-word rate that is competitive, and the per-line rate that sounds high can produce a per-word rate that is below market.

The Minimum Fee: Protecting Against Unprofitable Small Jobs

The minimum fee is the smallest amount the translator will accept for any project, regardless of pricing structure. The principle is that small projects carry the same overhead (project intake, file handling, invoicing, payment processing) as large projects, and the per-word or per-hour rate on a small project does not cover that overhead. A 100-word project at $0.15 per word is $15 — barely above the cost of the administrative time to set up the project and invoice for it.

The industry-standard minimum fee for freelance translators is $40-$80 per project, with the higher end for specialized work and the lower end for general content. Below the minimum, the translator either declines the project or charges the minimum (effectively raising the per-word or per-hour rate for the small project). A 100-word project at a $60 minimum fee is $0.60 per word — far above the standard rate, but justified by the overhead.

The minimum fee should apply across all pricing structures. A 30-minute editing project at $50 per hour ($25 total) should be billed at the $60 minimum, not at the per-hour rate. The minimum is not a surcharge; it is a floor below which the project is not worth taking. Translators who do not enforce a minimum fee end up working for $15-$20 per hour on small projects that consume administrative time disproportionate to the revenue.

The Rush Surcharge: Protecting Against Disruptive Deadlines

The rush surcharge is the premium added to the standard rate for projects with a deadline shorter than the translator's standard turnaround. The standard turnaround for a full-time freelance translator is typically 2,500-3,000 words per working day for general content, and 1,500-2,000 words per day for specialized work. A project with a deadline shorter than standard turnaround justifies a rush surcharge.

The rush surcharge schedule

• Standard turnaround (2,500-3,000 words per day): No surcharge
• 1.5× standard turnaround (e.g., 4,000 words per day): 25% surcharge
• Same-day or overnight turnaround (e.g., 6,000+ words per day): 50% surcharge
• Weekend or holiday turnaround: 100% surcharge
• Same-day weekend or holiday (the "impossible" deadline): 150%+ surcharge, or decline

The rush surcharge compensates the translator for three things: (1) the disruption of rescheduling other work to accommodate the rush project, (2) the cost of working outside normal hours (evening, weekend, holiday), and (3) the higher risk of errors under time pressure, which requires additional review time. Rush surcharges are not optional — they are the cost the client pays for prioritizing their project over the translator's other commitments. A translator who does not charge rush surcharges is subsidizing the client's poor planning with their own time and quality.

Rush surcharges apply on top of the standard rate, regardless of pricing structure. A per-word translator at $0.15 per word with a 50% rush surcharge charges $0.225 per word on rush work. A per-hour translator at $50 per hour with a 50% rush surcharge charges $75 per hour on rush work. The surcharge structure should be communicated to the client at the time of the quote, not added as a surprise on the invoice.

Choosing the Right Structure for Each Project

The right pricing structure depends on the type of work, the type of client, and the type of translator. The framework below is the decision tree most working freelance translators use to choose the structure for each project.

Use per-word when:

• The work is translation (not editing or proofreading)
• The source text has a measurable, reliable word count
• The client is an agency (agencies expect per-word pricing)
• The work is repetitive and CAT tool leverage will produce productivity gains
• The project scope is well-defined and unlikely to change

Use per-hour when:

• The work is editing, proofreading, or quality assurance review
• The source text is poorly written and throughput is unpredictable
• The work is project management, terminology research, or consulting
• The project scope is uncertain and likely to expand
• The client is a direct client who prefers per-hour billing (rare, but exists)

Use per-project when:

• The client is a direct client (not an agency)
• The project scope is well-defined and unlikely to change
• The work is high-value (sales copy, marketing campaigns, transcreation)
• The translator has the experience to scope accurately and defend the project fee
• The work involves non-translation deliverables (consulting, training, advisory)

Use per-line when:

• The client is a European agency that expects per-line pricing
• The translator's market is primarily German, Austrian, or Swiss
• The translator is comfortable with the per-line structure and the conversion math

Putting It All Together: A Worked Pricing Decision Example

Let's walk through the pricing structure decision for a mid-level English-Spanish translator (5 years experience, ATA certified) who has been approached for four different projects in a single week.

1. Project 1 — 8,000-word technical manual for an agency client: Per-word pricing at $0.18 per word (technical specialization multiplier) = $1,440. Standard turnaround, no rush. The CAT tool will deliver 60% TM match, so effective translation time is ~10 hours; effective hourly = $144/hour.
2. Project 2 — 3,000-word legal contract for a direct client: Per-project pricing at $900 (legal specialization, $0.30 per word equivalent, with project premium for direct-client value). The translator estimates 8 hours of work; effective hourly = $112/hour.
3. Project 3 — 12,000-word editing and proofreading of a poorly translated marketing document: Per-hour pricing at $65 per hour (1.3× effective per-hour translation rate for editing premium). Estimated 15 hours (poor source quality, 800 words per hour); project cost = $975; effective per-word = $0.08 (well below translation rate, but appropriate for editing work).
4. Project 4 — 200-word rush email translation for same-day turnaround: Per-word pricing at $0.15 per word × 200 words = $30, below the $60 minimum fee. Charge the $60 minimum, plus 50% rush surcharge on the per-word portion ($30 × 1.5 = $45). Total = $60 (minimum takes precedence). Effective per-word = $0.30; effective hourly for 30 minutes of work = $120/hour.

Across the four projects, the translator earns $3,375 for roughly 33.5 hours of work — an effective hourly rate of $100/hour, comfortably above the $100/hour floor for sustainable professional services work. A translator who priced all four projects at a flat per-word rate of $0.15 would have earned roughly $2,250 for the same hours — $67/hour, below the sustainable floor. The framework here is the difference between a sustainable translation career and a hobby that pays less than the translator's former W-2 job. Run it for your own projects with the freelance translator rate calculator, and if you also offer freelance writing services (where the per-word vs per-hour decision also applies), the freelance writer rate calculator applies a parallel framework for the writing market, where the per-word culture is even more dominant and the per-project case is even stronger for high-value content.