05 — Digital & Creative

Your product, native in Spanish — copy that converts, not copy that translates.

Localized product and UI copy that reads like it was written in Spanish, built for a recurring release cycle — strings and files, not just documents — with an optional engineering QA pass to catch what translation alone can break.

from €0.13 / word

At a glance

Languages

Spanish ⇄ English (core); other pairs on request

Turnaround floor

3–5 business days per batch (standard)

Delivery format

Strings, resource files or CMS export — not just documents

Tier

Full human translation, or machine-translated + human-post-edited

Who it's for

SaaS and e-commerce marketing or product teams launching a Spanish-market website, app or product update, usually on a recurring release cycle.

Typical documents

  • 01 UI strings and resource files (.json, .xliff, .po, .strings)
  • 02 Website page copy and CMS content
  • 03 App store listings
  • 04 Help-centre and knowledge-base articles
  • 05 Onboarding and in-product messaging
  • 06 Email and notification templates

Configure your website & software loc.

Spanish and English are our core pair. Type to see other European languages on request.

words

≈ 250 words per A4 page

Turnaround

For a recurring release cycle instead of a single batch, use /quote/ to set up a standing workflow.

Tier

Named honestly, and never the default — a deliberate choice for high-volume, lower-visibility strings.

Add-ons

A pass through the localized build to catch broken strings, truncation and layout breaks after translation — before it ships.

1000 words · €130.00

ex. IVA

Not sure of the exact count? → Send us the file

What's included

  • Translation that reads as native Spanish, not literal word-for-word rendering
  • Independent check by a second linguist before delivery (full-human tier)
  • File-format-native delivery (strings, resource files, CMS export)
  • Your choice between full human translation and the labelled MT-post-edited tier
  • Optional engineering QA pass on the localized build

How this service runs

01

Files & scope

Configure your batch, or set up a recurring workflow via /quote/ for ongoing releases.

02

Localized

Translated to read native in Spanish, by a linguist (full-human tier) or via the MT-post-edited pipeline.

03

Checked

Reviewed for tone, consistency and native-market fit; optional engineering QA pass checks the build itself.

04

Delivered

In your original file format, ready to merge back into your release.

Delivered as strings and files that drop back into your build — not a document you have to re-format into your codebase yourself.
Delivered as strings and files that drop back into your build — not a document you have to re-format into your codebase yourself.

Turnaround & pricing

Standard is 3–5 business days per batch; for an ongoing release cycle, /quote/ sets up a standing rate and workflow. The €65.00 minimum applies to any order under 500 words.

Full worked examples →

How every order is handled

Two-linguist review

Every order is completed by one linguist and checked by a second before delivery.

A legally defined sworn category

Traducción jurada is a regulated category under Spanish law — every certified order is prepared to that legal standard and delivered with a signed certification statement.

Confidentiality as standard

Documents are handled under a confidentiality process; an NDA is available on request.

Turnaround stated before you order

Standard, rush and express windows are shown before you add it to your cart.

Website & Software Localization FAQ

That's the point of the service — copy is localized to read native in the target market, not rendered literally word-for-word.

Files — UI strings, resource files (.json, .xliff, .po, .strings), and CMS exports are our default input for this service, not a special case.

Yes — that's what this service is built for. Set up a standing workflow via /quote/ so each new release's strings go through the same process.

It's a pass through your localized build looking for broken strings, truncated UI elements and layout breaks that translation alone can introduce.

The machine-translated, human-post-edited tier (−40%) is built for exactly that — named honestly, and something you choose deliberately.

Related services

Setting up a recurring localization workflow for your release cycle? Get a bespoke quote →

Price my localization

Price my localization