Weekly ecommerce tips, deals & news.
XLIFF stands for XML Localization Interchange File Format. It’s a standard file type that carries text out of your store, through a translator, and back again. Nothing gets lost on the way. Think of it as a courier envelope for words. The original stays put, and only the translatable text travels.
Store owners meet XLIFF the moment they hire professional translators. It’s the format that keeps your site structure intact while the language changes.
An XLIFF file is a text file built on XML, so it’s all labelled tags rather than formatting. Inside, your content is chopped into small units. Each unit holds one phrase, sentence, or field from your store.
Every unit has two halves. One half holds the original text, and the other sits empty until a translator fills it. Picture a bilingual exam paper, where the left column asks and the right column answers. That pairing is the whole point of the format.
Crucially, the file also carries context the translator needs. A unit can note where the text came from, whether it’s a product title or a button label. It can flag character limits too, which matters when a German phrase runs 40% longer than English.
The standard is maintained by OASIS, an open standards body. Version 1.2 was approved on 1 February 2008 and is still the most widely supported. The newer 2.1 release landed on 13 February 2018.
Each unit also carries a status. A phrase can be marked new, translated, reviewed, or final, depending where it sits in the process. That single detail is what lets a plugin re-export only the untranslated bits later. Without it, you’d resend everything and pay twice.
The workflow has four steps, and it’s simpler than it sounds. First, your translation plugin exports the pages or products you want translated. That export is the XLIFF file.
Second, you send that file to a translator or agency. They open it in professional translation software, which shows the source text and hides the technical tags. Third, they fill in every target slot and send the file back.
Fourth, you import the returned file. Your plugin reads each unit and drops the translated text into exactly the right field. As a result, nothing needs copying by hand, and nothing lands in the wrong place.
That round trip is where the “interchange” in the name earns its keep. Your store and the translator’s software may share nothing else in common. Still, both speak XLIFF, so the handover works.
Importing the words is only half the job, though. Search engines also need to know which language version to show which shopper. That’s handled by hreflang tags, which your translation plugin usually adds for you. Get them right and translated pages won’t be treated as duplicate content.
Plenty of stores do send spreadsheets, and it works until it doesn’t. The trouble starts with markup. Product descriptions contain links, bold text, and sometimes shortcodes, and all of that has to survive translation intact.
XLIFF wraps those elements in protective tags that translation software displays as locked placeholders. A translator can move a placeholder but cannot mangle what’s inside it. By contrast, a spreadsheet offers no such protection, so one stray character can break a link on every page.
The second advantage is memory. Professional translation tools build a database of previously translated phrases, and XLIFF feeds that database cleanly. If you sell 200 products that all mention “free returns within 30 days”, you pay to translate it once.
There’s a bookkeeping benefit too. Because each unit is tracked individually, you can see exactly what’s translated and what isn’t. Spreadsheets tend to drift out of sync the moment you edit a product.
Imagine a specialty tea importer called Leaf & Kettle. It runs a WooCommerce store with 400 products, all written in English. Sales are healthy at home, and the team wants to reach shoppers in Germany and Spain.
The commercial case is straightforward. English is the content language of 49.5% of websites. It is the first language of a far smaller slice of shoppers. Research across 29 countries found that 76% of online shoppers prefer buying products with information in their own language. In the same study, 40% said they would never buy from a site in another language.
So Leaf & Kettle hires a translation agency. Rather than emailing 400 product descriptions in a spreadsheet, the team exports XLIFF files from their translation plugin. Each file bundles the product titles, descriptions, and category names for one language.
Their descriptions are full of internal links to brewing guides. In an XLIFF file, each link becomes a locked placeholder the translator moves but never edits. Every single link still works after import.
Repetition pays off too. Roughly 60 of their products share the same steeping instructions, word for word. The agency’s translation memory recognises the repeat and charges a reduced rate for it.
Then a practical problem appears. The team adds 25 new teas mid-project, and those products need translating as well. Because their plugin tracks translation status per unit, it exports only the 25 new items. Nobody re-translates the original 400.
Finally, the import lands each translation in the right field automatically. The German product titles become German product titles, not description text. That accuracy is exactly what a spreadsheet cannot promise.
Most translation plugins offer a second route. You can type translations directly into a side-by-side editor in your admin area, skipping files entirely. Both approaches end in the same place, so the choice is about scale.
In-dashboard editing suits small jobs and in-house bilingual staff. It’s immediate, needs no file handling, and you see the result straight away. For twenty pages, it’s the obvious pick.
XLIFF suits volume and outsourcing. External translators rarely want logins to your store, and professional tools genuinely speed their work. On top of that, files create a clear paper trail of what was sent and returned.
A rough rule helps here. Under roughly 50 items with your own team, translate in the dashboard. Beyond that, or with an outside agency, use XLIFF.
The two methods also mix happily. Many stores translate their core pages in the dashboard, then batch product catalogues out as files. Nothing forces you to pick one approach for the whole site.
Technically yes, but you shouldn’t. Word and Excel will show you raw tags mixed into the text, which is confusing and easy to damage. Worse, saving from those programs can corrupt the structure so your store rejects the import. Use free translation software instead, or send the file to someone who has it.
No, it’s optional. Translation plugins let you enter translations directly in your dashboard, and machine translation can handle a first pass. XLIFF becomes worthwhile once you outsource the work or handle hundreds of products. Bulk imports and exports of product data are a separate job, handled by tools like Product Importer Deluxe.
Version 2.1 is a cleaner, stricter redesign with better support for modern workflows. Version 1.2 is older but far more widely supported across tools. In practice, most store owners never choose, because the plugin picks a version for them. If an agency reports an import problem, the version is worth checking first.
XLIFF is the plumbing that makes professional translation practical at scale. You’ll never write one by hand, but knowing what it does explains why translators ask for it. For any store selling in more than one language, that handover format keeps quality and structure intact.
Copyright © StoreOwnerTips.com. All Rights Reserved.
