Preparing PSD, SVG, XTG, Excel, and Word Files for Localization and XLIFF Exchange
Extract editable text from PSD, SVG and XTG files, round-trip XLIFF with your CAT tool, prepare Excel cells, and repair Word language and direction.
- Extract live text from PSD, SVG, and XTG files into XLIFF; outlined or rasterized text is geometry, not strings.
- Exchange text through XLIFF with your CAT tool or hand it to BLoc Translate; the prep tool never translates itself.
- Reassemble localized content into separate output copies so originals stay untouched and reviewable.
- Prepare only explicitly selected Excel cells and apply only chosen Word language, font, and direction repairs.
2Translate) never overwrites your source files. In Excel, you explicitly choose between accepting unverified cached formula strings or running controlled recalculation through installed Excel, leaving unselected formulas untouched. In Word, you can export a read-only inspection report or save a reviewed copy accompanied by JSON and Markdown manifests verified by source SHA hashes.Design files stall localization projects in a specific way: the text is inside a Photoshop composite, an SVG path group, or a Tagged Text archive that no CAT tool can open, so the studio receives the translated Word file and a pile of flattened artwork and starts retyping. Retyping is where errors are born — a dropped diacritic, a truncated string, a paragraph pasted into the wrong layer. BLoc Localization Prep replaces that retyping stage with an engineering step: text is extracted into a translatable format, exchanged through XLIFF, and reassembled into a separate localized copy of the design file. This guide covers the preparation workflow for PSD, SVG, and XTG artwork, selective Excel preparation, and Word inspection and repair.
Why studios receive untranslated design files
The failure pattern is consistent across agencies. Designers produce artwork with live text in formats the localization pipeline cannot read, the translation team works around it by exporting screenshots and typing translations into a chat, and the studio then rebuilds the layout manually with the translated strings. The costs stack up quietly: every manual retyping is a defect opportunity, every rebuild is unbilled effort, and the localized artwork never quite matches the approved source design. Meanwhile nobody can say which string in the artwork corresponds to which row in the translation file, so even the corrections loop breaks.
The fix is to treat design text as content engineering, not as a designer's afterthought. Text leaves the design file in a structured exchange format, translation happens in a dedicated tool, and translated text returns to a rebuilt design copy. Originals are never touched, because the pipeline writes to separate output files — which also means the source design remains the single source of truth for everything except language.
Extracting editable text from PSD, SVG, and XTG
BLoc Localization Prep extracts editable text from supported PSD, SVG, and XTG files. Each format carries text differently, and the extraction step is where preparation earns its keep:
- PSD — Photoshop composites hold text in layers; extraction pulls the editable layer text into the exchange package so captions, headlines, and labels become translatable strings.
- SVG — vector graphics used across web and print embed text elements; extraction captures the editable text rather than the outlines, preserving the file's structure for reassembly.
- XTG — Tagged Text archives from layout work carry styled paragraphs; extraction turns them into exchangeable segments without losing the tagging that will steer reassembly.
Extraction is bounded by what the file actually contains: text that was rasterized or converted to outlines before the file arrived is not editable text, and no preparation tool can recover it as strings. That is why the correct time to fix "flatten everything" habits is before the file reaches localization — keep live text layers in the handoff version of every design file. Supported file structures and Adobe requirements are confirmed for your workflow, so validate one representative file per format when onboarding a new client rather than discovering boundaries mid-project.
The XLIFF round trip: CAT tools and BLoc Translate
The extracted text is exchanged as XLIFF, the standard interchange format every serious localization toolchain already speaks. That gives you two routes, and the choice is organizational rather than technical:
- Route through your CAT tool. The XLIFF package goes to the translator's normal environment, where existing translation memories, term bases, and QA checks apply. The localized file returns through the same exchange.
- Route through BLoc Translate. The XLIFF is uploaded to the batch AI translation workflow, where assigned templates provide translation memory, terminology, and writing rules, and the translated result returns as part of the batch — see batch AI file translation with terminology and templates.
What Localization Prep itself does not do is translate: translation is performed in BLoc Translate or another translation tool, and the preparation tool's job is the honest plumbing in both directions. Keep the XLIFF files versioned alongside the design files they came from. When a reviewer asks why a caption reads differently from the approved glossary, the exchange file is the evidence of what was sent and what came back.
Reassembling localized copies without overwriting originals
Once translated segments return, reassembly writes the localized content into a separate design copy ready for layout review. The reviewer then checks what any localization engineer checks: does the translated text fit the frames, did bidirectional content keep its correct direction, did styling survive the round trip, and are there strings that came back longer than the layout can hold. Where a layout change is genuinely needed, it happens in the localized copy under review — not in the source, and not invisibly.
This separation has a second-order benefit for versioning. The source file keeps its identity as the master for the next language and the next update; each localized copy is traceable to the source version and the XLIFF exchange that produced it. Teams that merge everything into one file lose exactly this traceability, and with it the ability to answer "which version of the artwork is this translation based on?"
Excel: preparing the cells that need translation
Workbooks are the least glamorous and most error-prone part of localization prep. A product workbook mixes UI strings, comments, formulas, part numbers, and internal notes, and translating the whole sheet is how a formula becomes a sentence. BLoc Localization Prep inspects the workbook and prepares explicitly selected text cells — you choose what enters the localization package, and everything else stays exactly as it is.
| File family | What gets prepared | What stays untouched |
|---|---|---|
| PSD / SVG / XTG | Editable text extracted to XLIFF; rebuilt into separate localized copies | Original design files and all non-text layers |
| Excel workbooks | Only the text cells you explicitly select | Formulas, unselected cells, workbook structure |
| Word documents | Language, font, and direction repairs you choose to apply | Document content and anything you do not confirm |
Selective preparation is also a quality control. A cell containing a SKU, a URL, or a build number should never enter translation, and the selection step is where that discipline is enforced. When the workbook returns, review the changed cells against the source selection — the reviewed Office copy is a separate output, so the original workbook remains the system of record.
Word: language, fonts, and direction inspection and repair
Word documents carry localization state in their formatting: proofing language assignments, fonts with and without the target script's coverage, and paragraph direction. A document that "looks fine" in Latin script can misbehave the moment Arabic or another RTL language arrives, because the underlying language and direction attributes were never set for it. Localization Prep reviews Word language, fonts, and direction, and then applies the repairs you choose — the inspection produces findings and options, not silent changes.
A practical repair sequence: inspect the document's language assignments and correct them so proofing and shaping behave; check font coverage for the target script and pick repairs where substitution would otherwise occur; and fix direction attributes on the paragraphs that need them. Then review the selected changes in the output copy, because a repaired document still deserves the same layout review as any other localization output. For documents destined for PDF distribution, the typeset result should pass through BLoc PDF QC before delivery — the review workflow is covered in turning translated PDF reviews into clear DTP corrections.
Pre-delivery engineering checklist
- Confirm every design file in scope has live text layers where translation is expected, and flag outlined or rasterized text as out of scope.
- Extract text from PSD, SVG, and XTG files and validate the XLIFF packages load in the chosen translation route.
- Select Excel text cells explicitly, and verify formulas, identifiers, and unselected cells are excluded.
- Run the Word inspection, choose repairs for language, fonts, and direction, and record what was applied.
- After translation, reassemble localized design copies and review fit, direction, and styling against the source design.
- Verify originals are unmodified and output copies are correctly named and versioned alongside their XLIFF exchanges.
- Route typeset PDF deliverables through PDF QC before release.
- Archive source files, XLIFF exchanges, and reviewed output copies together so the lineage is reproducible.
Technical FAQ
Does Localization Prep translate my text?
No. Translation is performed in BLoc Translate or another translation tool. Localization Prep prepares content, exchanges text through XLIFF, and rebuilds supported files for layout review. Keeping translation and preparation separate is what lets each step be reviewed on its own terms.
Can I send the XLIFF to my CAT tool instead of BLoc Translate?
Yes. The XLIFF exchange works with your CAT tool, so existing translation memories and term bases apply, or you can hand the package to BLoc Translate for template-guided batch translation. Choose per project, and keep the choice consistent within a delivery so review stays comparable.
Will my original PSD or workbook be modified?
No. The workflow keeps original files and creates separate output copies. Rebuilt designs and selected Office changes are reviewed before delivery, and supported file structures plus Adobe or Office requirements are confirmed for your workflow. The originals remain your master files throughout.
What if some text in my SVG is actually outlined paths?
Outlined letters are geometry, not text, and extraction cannot turn them back into strings. Rebuild those elements as live text in the handoff file before extraction, or plan for the affected strings to be handled as artwork. Validate one representative file per format when onboarding, so structure boundaries are known before the project scales.
Walk through the Localization Prep interactive walkthrough to see the preparation steps in order, and check the BLoc Localization Prep tool page for the full feature list. Preparation is unglamorous work, but it is the difference between a studio that retypes and a pipeline that rebuilds.
Related guides
BLoc Localization Prep · File preparation
Ready to apply this workflow in production?
Prepare design and Office files for localization, hand text to your translation workflow, and review rebuilt results. Pricing: $15 / month or $150 / year.