Website and Multimedia Translation Services

Digital and multimedia localisation for UK businesses expanding into multilingual markets sits inside our full Translation Services catalogue as one continuous linguistic-asset pipeline — source text moves into a shared translation memory, then out to websites, apps, subtitles, and voiceover under ISO 17100 quality control from our London base.

Which digital and multimedia assets do you localise?

We localise six digital asset classes: marketing websites, ecommerce stores, software and mobile apps, subtitles and closed captions, voiceover and dubbing tracks, and multilingual SEO content. Each class routes to a dedicated sub-service under the same ISO 17100 translation memory, so terminology remains consistent across every channel and every deliverable format.

Asset class	Deliverables	File formats	Pricing unit
Website	Localised pages, metadata, structured data	HTML, XML, XLIFF, WPML export	Per page / per word from £30
Ecommerce	Product copy, checkout, VAT-inclusive pricing	CSV, PO, XLIFF, platform export	Per word
Software & app	UI strings, pseudo-loc QA, build-ready bundles	.strings,.xml,.json,.resx, XLIFF, PO	Per source word
Subtitling & CC	Time-coded SRT/VTT/TTML, SDH captions	SRT, VTT, TTML, MP4, MOV	Per audio minute
Voiceover & dubbing	Translated script, native voice talent, mixed stems	WAV, MP3, MP4	Per recorded minute + talent
Multilingual SEO	Localised keywords, meta titles/descriptions, hreflang, anchors	CMS export, XLIFF	Per localised URL

How does website translation and localisation work?

Website translation and localisation converts source HTML, CMS content, and UX copy into the target locale, adapting currency symbols, date formats, and legal notices — including GDPR-compliant cookie banners and UK Data Protection Act 2018 consent copy — while fully preserving SEO metadata and structured data markup. Full site scope covers page copy, metadata, structured data, and CMS-integrated content across 200+ languages. Localisation goes beyond literal translation to adapt currencies (GBP, EUR, USD), date rendering (DD/MM/YYYY for en-GB), and cultural references so the site feels native to each target market rather than merely translated.

• en-GB vs en-US spelling divergence (colour/color, organise/organize) handled at the locale level.
• GBP with VAT-inclusive display for UK ecommerce pages.
• DD/MM/YYYY date rendering and 24-hour time conventions applied for UK locale.
• GDPR and UK Data Protection Act 2018 cookie banners and consent copy translated with equivalent legal meaning preserved.
• hreflang tags mapping each URL variant to its correct language-region pair for multilingual search visibility.

How do you translate ecommerce stores?

Ecommerce translation localises product titles, descriptions, checkout flows, VAT-inclusive pricing, and shipping notices, integrating with the four major ecommerce platforms — Shopify, WooCommerce (via WPML), Magento, and BigCommerce — through export and import of PO, XLIFF, and CSV catalogues. Every translated catalogue segment passes through the shared TM, so product terminology stays consistent between the storefront, the checkout confirmation email, and any in-app purchase flow running on the same termbase.

• Platforms supported: Shopify, WooCommerce (WPML), Magento, BigCommerce.
• Catalogue formats: CSV, PO, XLIFF, JSON, and native platform export files.
• Locale adaptation: currency symbols, VAT rules, shipping zone copy, and return-policy wording for each target market.

How is software and mobile app localisation delivered?

Software and mobile app localisation processes.strings,.xml,.json,.resx, XLIFF, and PO resource files, handles pluralisation rules and placeholder variables, and returns build-ready bundles for iOS, Android, and web single-page applications complete with pseudo-localisation QA to catch truncation and text-expansion issues before the build. XLIFF serves as the open interchange standard that allows source strings to move cleanly between the development environment, the CAT tool, and our translators without data loss or formatting corruption.

1. Extract translatable strings from.strings (iOS),.xml (Android),.resx (.NET),.json (web), and PO (open-source frameworks).
2. Lock placeholder variables (%@, %s, {name}) and ICU MessageFormat plurals to prevent corruption during translation.
3. Translate under the shared TM with in-context screenshots supplied where available.
4. Run pseudo-localisation to surface UI layout breaks caused by text expansion before the localised build is cut.
5. Return build-ready resource bundles with a final linguistic QA sign-off under ISO 17100.

How are subtitles and closed captions produced?

Subtitling and closed captioning delivers time-coded SRT, VTT, and TTML files at a controlled reading speed of 15–17 characters per second, with SDH captions that include speaker identification and sound descriptions for deaf and hard-of-hearing viewers. All subtitle output meets Ofcom’s quality and accessibility standards for UK on-demand video services. Captions are authored directly in the target language rather than machine-generated and post-edited, ensuring that timing, line breaks, and reading speed comply with broadcast conventions across every locale.

• Deliverable formats: SRT, VTT, TTML — supplied alongside the original media file on request.
• Reading speed: 15–17 characters per second, calibrated for comfortable comprehension.
• SDH captions: include speaker labels and non-speech audio cues for accessibility compliance.
• Compliance: output meets Ofcom subtitle quality requirements for UK on-demand platforms.

How is voiceover and dubbing handled?

Voiceover and dubbing services cover UN-style voiceover, lip-sync dubbing, plain narration, and e-learning voiceover, each produced by native-speaking voice talent working from a script that has passed the same ISO 17100 translation and revision process as every other asset type. UN-style voiceover lays the translated audio beneath the original speaker’s voice at a slightly lower volume — the format most used for documentary and corporate interview content. Lip-sync dubbing replaces dialogue entirely, matching syllable timing and mouth movement to the on-screen performance. E-learning voiceover is timed to slide animations and interactive cues, with the translated script reviewed by an instructional context specialist before recording begins.

• Modalities: UN-style voiceover, lip-sync dubbing, narration, e-learning voiceover.
• Deliverable formats: WAV and MP3 stems for audio, MP4 for finished mixed video.
• Pricing unit: per recorded minute plus voice talent, quoted in GBP before work begins.

How does multilingual SEO content work?

Multilingual SEO localises target keywords for each market, rewrites meta titles and meta descriptions to fit character limits in the target language, maps hreflang attributes to every URL variant, and translates internal anchor text so link equity passes correctly through the localised site architecture. Keyword localisation is not a direct translation of English search terms — it is a fresh research process in the target language that identifies how local users actually phrase their queries, then integrates those terms naturally into the page copy and metadata the translator produces.

• Deliverables: localised keyword sets, meta titles and descriptions, hreflang mapping files, and translated internal anchors.
• Process: locale-specific keyword research followed by on-page integration, not mechanical term substitution.
• Technical output: hreflang annotations supplied in XML sitemap or HTML head format, ready for CMS upload.

How fast can website and multimedia translations be delivered?

Turnaround is tiered by volume and asset type: same-day delivery in London applies to digital assets under 1,000 source words ordered before 11:00 GMT; standard website packs, subtitle files, and app string bundles between 1,000 and 10,000 words are delivered within 24 to 48 hours; and projects above 10,000 words — including full site localisations, complete app releases, and multi-reel dubbing jobs — are delivered against an agreed milestone schedule. Every tier runs under ISO 17100 quality control, meaning a qualified translator and an independent reviser both work the file before it leaves our hands.

Audio-visual turnaround is governed by media duration rather than word count. A subtitle file for a ten-minute product video is returned within 24 hours; a full-length training course with voiceover is scheduled as a milestone project with staged script approval, voice recording, and final mix across several working days. Same-day voiceover is available for short clips — provided the translated script is confirmed before the 11:00 GMT London cutoff.

Tier	Volume	Turnaround	Typical asset
Same-day	Under 1,000 source words	Same working day (11:00 GMT cutoff)	UI strings, landing pages, short subtitle chunks
Standard	1,000–10,000 words	24–48 hours	Product pages, SRT/VTT files, app string updates
Milestone	Above 10,000 words	Staged delivery on agreed schedule	Full site localisation, app release, dubbing project

Rush handling is available outside standard tiers on request — contact us with your volume and deadline and we will confirm capacity within the hour alongside a fixed GBP quote.

Which UK and EU compliance rules apply to localised digital content?

Localised digital content in the UK is subject to several overlapping regulatory frameworks. GDPR and the UK Data Protection Act 2018 govern translated cookie banners, consent flows, and privacy notices — every localised version must convey the same legal meaning as the English source, and any ambiguity introduced by imprecise translation creates compliance exposure for the site owner. We treat consent copy as a regulated document class, applying ISO 17100 revision as standard and flagging any source text that is itself legally ambiguous before translation begins.

• GDPR / UK Data Protection Act 2018: translated cookie banners, consent flows, and privacy notices must preserve full legal equivalence with the source. Cookie banners, consent copy, and privacy notices on UK sites all fall within scope.
• Ofcom: regulates subtitle quality and accessibility on UK on-demand video services; our SRT, VTT, and TTML output is produced to meet Ofcom’s published subtitle standards, including reading speed and SDH caption requirements.
• Equality Act 2010: requires accessible captions and SDH tracks for deaf and hard-of-hearing audiences on UK-facing digital content.
• ASA (Advertising Standards Authority): translated marketing claims must remain substantiated and non-misleading in the target language — literal translation of a claim does not automatically preserve its evidential basis.
• EU Web Accessibility Directive (2016/2102): mandates WCAG 2.1 Level AA (via EN 301 549) for public-sector websites and apps, including captions for all pre-recorded video content.

Regulated sectors — including healthcare, legal, and financial services — require translated web content and app copy to be reviewed by subject-matter experts or certified translators. Our ISO 17100 workflow builds that second-linguist review into every project as a mandatory step, not an optional add-on, so sector-specific compliance requirements are met at the process level rather than managed retrospectively.

How do website, app, subtitle, and voiceover assets share one translation memory?

All assets share one translation memory by feeding every source segment — web copy, UI strings, subtitle lines, and voiceover scripts — into a single CAT tool project keyed to the client’s termbase, so a product name approved on the website appears identically in the iOS app, the SRT caption file, and the dubbed audio script. The TM is a shared segment repository that stores every previously approved translation and reuses it automatically whenever the same or similar source text recurs across any asset type, keeping terminology consistent and cutting the cost of repeat content.

The pipeline runs as one continuous linguistic-asset flow rather than six parallel jobs managed by separate teams. When the marketing team signs off “Smart Ledger” as the approved product name in en-GB, that term is locked in the glossary immediately. Every subsequent segment touching that term — the Android onboarding string in the.xml resource file, the SRT caption on the product demo video, the voiceover script for the e-learning module — pulls the same approved form automatically without requiring a manual check. This is the mechanism that closes the terminology drift gap: without a shared TM, the same concept is rendered differently by the web translator, the app localiser, and the subtitle editor, creating brand inconsistency that is costly to audit and correct after publication.

Cost efficiency is a direct outcome of TM reuse. Segments that match a previous translation at 100% are leveraged at a reduced rate; high fuzzy matches (75–99% similarity) attract a proportional discount. Across a large digital estate — website, app, help centre, and subtitle library — accumulated TM leverage regularly reduces the per-project word cost as the repository grows, rewarding clients who consolidate all their digital localisation under one workflow.

How do you quote a website and multimedia localisation project?

Send the source URL, repository, or media file with your target languages and deadline, and we return a fixed GBP quote within one business hour, itemised by asset class — per page or per word for websites, per audio minute for subtitles and voiceover, and per source word for app resource files — with ISO 17100 revision and same-day London cutoff options clearly indicated. Pricing starts from £30 per page for website content, with audio-visual and app rates confirmed once we have reviewed the source material.

1. Submit your source material: share a URL, GitHub repository, ZIP of resource files (.strings,.xml,.json,.resx, PO, XLIFF), or a video file link, together with your target language list.
2. State your deadline: confirm whether same-day delivery (11:00 GMT London cutoff, under 1,000 words) applies, or specify a standard or milestone schedule.
3. Receive an itemised GBP quote: within one business hour, broken down by asset type and language pair, with ISO 17100 translation and independent revision included as standard.
4. Confirm the termbase: supply any existing glossary, a list of do-not-translate terms, and approved product or brand names so the TM is seeded correctly before work begins.
5. Receive staged delivery: output is delivered per the agreed schedule — same-day, 24–48 hours, or milestone — with a certificate of accuracy available on request for regulated or compliance-sensitive content.

Projects spanning multiple asset types — for example a website localisation paired with subtitle files and an app string update — are quoted as a single consolidated scope, with the shared translation memory applied across all assets from day one to maximise terminology consistency and TM leverage discounts from the outset.