PolyGrid

PolyGrid

Excel <> XLIFF Localization Studio

6 followers

PolyGrid is an Excel ↔ XLIFF localization studio for multilingual teams. Convert messy spreadsheets into CAT-ready XLIFF and merge translations back with formatting preserved. It supports XLIFF 1.2 and 2.1, built-in and custom SRX segmentation, MT prefill via DeepL or Google, and processes files fully in memory with zero storage. Works with all major CAT tools. Start free, upgrade as you scale.
PolyGrid gallery image
PolyGrid gallery image
PolyGrid gallery image
Free Options
Launch Team / Built With
AppSignal
AppSignal
Get the APM insights you need without enterprise price tags.
Promoted

What do you think? …

Kaan Demirel
Maker
📌

Hey Product Hunt! 👋

I've spent close to 10 years as a software engineer in the localization industry, building end-to-end l10n workflows for various companies. One thing that always frustrated me: the gap between Excel spreadsheets and professional translation tools.

The inspiration for PolyGrid came from Okapi Framework, a powerful open-source library I used constantly in my workflows. Okapi is great, but it has a steep learning curve and requires technical setup. On the other end, handling Excel conversions through CAT tools means paying for expensive licenses, UI learning curve, creating projects just for text extraction/merging.

PolyGrid sits in the sweet spot: easier than Okapi, cheaper than CAT tools. Perfect tool for: 1) solo translators who don't want to translate on Excel and move client files to the CAT tool of their choice, 2) small localization teams that manage Excel localization projects, 3) localization engineers/PMs that are tasked with preparing Excel files for translation.

Upload your Excel, configure your columns, get XLIFFs. Send to translators. Merge translations back, formatting and formulas preserved.

What I'm proud of:
Built-in segmentation with custom SRX support
Ability to convert multilingual sheets into XLIFFs natively and bulk merging translated XLIFFs in one go.
MT prefill with DeepL or Google
Privacy-first: files processed in memory, never stored

Would love feedback from anyone dealing with spreadsheet localization. What's the most painful part of your current workflow?