Localization.One bridges the gap between developers and translators. Export your project strings to a universal CSV format that can be opened in Microsoft Excel, Google Sheets, or any spreadsheet software.
Why use our CSV Export?
- Universal Compatibility: Open your localization data in Microsoft Excel, Google Sheets, or any spreadsheet software for viewing and analysis.
- Excel Ready: Our files include a BOM marker, ensuring correct character encoding (UTF-8) when opened directly in Excel. No more broken characters.
- Data Backup: Keep a local offline copy of all your translations for security and compliance.
Advanced Project Management
We provide powerful tools to keep your localization organized, no matter how large your project grows.
Categorization: Group your strings into a logical folder tree (e.g., Marketing > Emails, Legal > Terms).
Labels & Tags: Mark strings with custom labels to filter which specific parts of the project you want to export to CSV.
Roles & Permissions: Invite unlimited team members and assign granular roles (Owner, Admin, Manager, Translator).
Webhooks: Receive notifications on your server whenever translations are updated or approved.
How to Integrate
Option 1: Manual Export (UI)
Useful for sharing files with translators.
- Go to your Project Dashboard.
- Click the Download button.
- Select CSV (Excel) from the format dropdown.
- Choose the language and download the .csv file.
Option 2: Automate with API
Fetch the latest translations as a CSV file for reporting or backup purposes. Pass the format=csv parameter.
bash
# Download English translations as CSV
curl "https://api.localization.one/{YOUR_API_KEY}/getTranslations?translation_language=1&format=csv" > export_en.csvOption 3: Push via Webhooks
Configure a Webhook URL in your project settings to receive notifications about translation updates.
- Quick Updates: Your server receives a POST request shortly after changes (usually within 5 minutes).
- Sync External Systems: Automatically push updates to 3rd party TMS or reporting tools.
Frequently Asked Questions
Does the file support special characters?
Yes. We add a UTF-8 BOM marker to the beginning of the file. This ensures that Microsoft Excel opens the file with correct character encoding, even for languages like Cyrillic, Chinese, or Arabic.
Can I import this file back?
Currently, this format is for export and reporting purposes only. We recommend making edits directly in the Localization.One interface to ensure version control and consistency.
Integrate with code:
- Need a developer format? Check out JSON for React or PHP for Laravel.
Ready to streamline your localization workflow? Create your free account today.