Sizing

Strategies to optimize translation quality and speed

Optimal Request Size

Recommended: Keep translation requests under 1,500 words for best results.

Why this matters:

  • Requests over 1,500 words are automatically split into multiple tasks
  • Split requests are usually handled by different translators in parallel
  • This can impact consistency and context understanding

Quality Through Context

Group Related Content:

Bundle related text chunks together instead of sending individual sentences. This approach helps translators:

  • Work more efficiently with better context understanding
  • Maintain consistency across related content
  • Deliver faster results with improved quality
  • Review larger amounts of text for better accuracy

Best Practices

✅ Do This

  • Combine related sentences into single requests
  • Group by topic or section (e.g., all product descriptions for one category)
  • Keep requests under 1,500 words to avoid automatic splitting
  • Provide context through related content grouping

❌ Avoid This

  • Single sentence requests - translators lack context
  • Unrelated content mixing - makes translation inconsistent
  • Requests over 1,500 words - gets split among multiple translators
  • Random content grouping - reduces translation quality

Processing Workflow

  • Pre-processing: We automatically process Translation Requests before sending to translators to optimize workflow and quality.
  • Splitting Logic: Requests exceeding 1,500 words are divided into separate tasks, typically assigned to different translators working in parallel.
  • API Limits: While our API limits allow much larger requests, staying under 1,500 words ensures optimal translation quality and consistency.

Examples of Good Sizing

E-commerce Product Page:

  • Product title, description, features, and specifications (grouped together)
  • Customer reviews for the same product (grouped separately)

Marketing Campaign:

  • Landing page copy: headline, subheading, body text, and CTA (grouped together)
  • Email campaign content (grouped separately)

Documentation:

  • One feature guide or tutorial (grouped together)
  • FAQ section for related topics (grouped together)

Following these guidelines ensures your translations maintain context, consistency, and quality while being delivered as quickly as possible.