Alconost is a tech-driven localization company building an ecosystem of products around localization and QA.
Since 2004, we've helped companies of all sizes, from indie app and game developers to industry leaders, reach audiences in 120+ languages. We combine linguistic expertise, cultural intelligence, and advanced technology to handle every aspect of global expansion.
Flexible teams, purpose-fit service levels for any budget, and effective delivery at any volume and speed.
This is the 8th launch from Alconost Localization Lab. View more
Glossary Extractor
Launched this week
Every serious localization project needs a glossary – and pulling the right terms out of your content by hand is slow, repetitive work. This tool does it for you: upload a file, get a structured term base back in minutes, with each term defined, counted, and (if your file is multilingual) translated. It pairs algorithmic term-finding with an AI cleanup pass, so the result is accurate enough to ship with just a quick review. It's free and requires no signup.
Free
Launch Team
Alconost Localization Lab
@margarita_s88 Congrats on the launch!! And I'm sure any tool that does the "boring" stuff would be very popular. I'm not familiar with localization like this but is the primary problem your product solves time savings?
Alconost Localization Lab
@anna_ludwinowski thanks very much for your support, Anna! <3 yes, the primary benefit is saving time and effort. We are always trying to find a way to make the process more efficient and fast, while keeping the quality up.
We made this mainly for localization teams and LSPs – the people who know how long terminology prep really takes. It's part of a small ecosystem of tools we're building, and yes, some of them (this one included) are free, partly as our contribution to the industry. Would really love to hear from other loc folks here: what does your current terminology workflow look like?
Hi Product Hunt! We built this because prepping terminology for a localization project is often a time-consuming task – and with our Glossary Extractor it can be done much faster. The tool does the boring part: an algorithmic pass pulls candidate terms from your file, then AI removes the noise, and the counts are calculated exactly in code (not guessed by a model). You upload what you already have – JSON, XLIFF, Excel, CSV, plain text – and get a structured glossary back in minutes. It's free. Would love your honest feedback.
How is this more accurate than just asking ChatGPT to pull out terms?
Alconost Localization Lab
@anastasiya_sabalenka A pure AI approach tends to invent terms and miscount, and making the model count every term across a whole document is slow and expensive on top of being unreliable.
Here, a fast algorithmic pass builds a shortlist straight from your actual text and handles the counting exactly, then the AI only reviews that shortlist - dropping false terms and catching real ones it missed. Using each method for what it's best at means less noise, accurate counts, lower cost, and far less manual cleanup.
Hope that answers your question :)
Mailwarm
What file types does it handle best, like docs and PDFs, or plain text and spreadsheets?
Alconost Localization Lab
@karimbenkeroum Thank you for your question! Actually we haven't noticed any correlation between the file type and the results. That said, if you have translations alongside your source text, it's best to use a format that separates the languages into columns (like CSV or Excel) - that way the tool can pick up the translations and include them per language.
Will it handle a large file? Are there any limits on the file size or word count?
Alconost Localization Lab
@liza_diagel There's no upper size limit, large files just take a little longer. It does need at least ~500 words to have enough context to extract reliable terms. The only setting you control is Max Terms, which caps how many terms land in the final glossary (default 500).
Does the tool translate the terms itself?
Alconost Localization Lab
@uladzimirku No - it's an extractor, not a translator. Translations only appear if they're already in your file (a translation memory or a bilingual document). From a monolingual file you get a clean list of terms without translations.