The file you send for software localization can affect what your provider can translate, how context is preserved, and how smoothly the localized content returns to your product. A spreadsheet may be easy to review, while a resource file can retain identifiers and structure. Neither is automatically the right choice for every project. Match the format to your platform and workflow, then share the supporting details your provider needs to handle text accurately without changing functional content.
Compare common file types
Resource files such as JSON, XML, YAML, and platform-specific string files can keep text linked to keys, tags, or interface structure. They are often suitable when your software already uses them and your localization workflow can process them safely. Confirm which fields are translatable and whether the provider can preserve markup, variables, and ordering. A valid file is not necessarily a localization-ready file.
CSV and spreadsheet files make content easier for people to inspect, comment on, and approve. They work well for controlled lists of strings, but can lose important structure if columns, identifiers, or formatting change. Define which columns contain source text, context, status, and translation. Protect formulas and other non-text cells, and agree how the completed file will map back into the product.
Choose based on your workflow
Start with the files your development team can reliably export and re-import. If your product uses a standard resource format, sending that format may reduce manual copying and help retain identifiers. If reviewers need a spreadsheet, provide an approved export rather than asking someone to rebuild files by hand. Test the round trip with a small sample before sending a large content set.
Consider how often content changes, who reviews it, and whether strings need screenshots or developer notes. A continuous localization platform may accept files directly or connect to a repository, while a one-time release may use a controlled file exchange. Ask your provider to confirm supported formats, encoding, file-size limits, and any handling requirements before you prepare the full package.
Share context, not just files
Send a glossary, style guidance, and product background when available. Explain the audience, software purpose, target languages, and where each set of strings appears. Add notes for ambiguous labels, character limits, variables, and text that should remain unchanged. Context helps translators distinguish, for example, a command from a descriptive label without relying on guesswork.
Include screenshots or a test build when the text depends on layout, nearby controls, or user actions. Identify the source-language version and provide a contact who can answer product questions. Also state whether your provider should translate comments, hidden strings, or text embedded in images. Clear instructions prevent out-of-scope content from being altered or overlooked.
Protect structure and verify delivery
Before transfer, remove obsolete strings and confirm that the files open correctly. Keep a clean backup of the source, use consistent filenames, and avoid changing keys or tags after translation begins. Tell the provider which elements are placeholders, such as {user_name} or HTML markup, and whether these must stay exactly as written. Use a secure transfer method approved for your company’s content.
Agree on what the returned files should include: translated text, preserved identifiers, notes on queries, and any agreed status fields. Have your development team import a sample and check for broken syntax, missing strings, clipped text, and display issues. A translation can be linguistically sound yet still need adjustment to fit an interface or function correctly.
Choose a format that fits your product and can be safely returned to development, then pair it with context, clear handling instructions, and a plan for testing. If you are unsure which files to prepare, Meridian Technical can help you review your localization materials and agree on a practical handoff.