This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Translates your JSON locale files incrementally — only strings that actually changed since the last run are sent for translation. The translator is fully configurable: use any LLM, any free translation service, or implement your own.
Transly translates your i18n JSON locale files incrementally — only strings that actually changed since the last run are sent for translation.
The translator is fully configurable: use any LLM, any free translation service, or implement your own.
What it does
On each run transly scans your source locale directory, computes a SHA-256 hash of every string, compares it against a local cache, and translates only the keys that are new or changed. Translated strings are written to the target language directories and the cache is updated. If a batch fails mid-run, everything translated so far is already saved — just re-run to continue.
Why transly
- Only translates what changed, based on content hashes — not git history, not timestamps
- Cache is written after every chunk, so partial failures never lose work
- Translator backend is pluggable: LLM, free API, or your own function
- Works without any LLM config at all (falls back to a free translation service)
- Concurrent translation of multiple namespace × language pairs
No comment highlights available yet. Please check back later!
About Transly on Product Hunt
“Cache-driven incremental translation tool”
Transly was submitted on Product Hunt and earned 3 upvotes and 1 comments, placing #158 on the daily leaderboard. Translates your JSON locale files incrementally — only strings that actually changed since the last run are sent for translation. The translator is fully configurable: use any LLM, any free translation service, or implement your own.
Transly was featured in Languages (14.3k followers), Developer Tools (511.7k followers), GitHub (41.2k followers) and Development (5.8k followers) on Product Hunt. Together, these topics include over 94.4k products, making this a competitive space to launch in.
Who hunted Transly?
Transly was hunted by Robert Vitonsky. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Transly stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Robert Vitonsky
Transly translates your i18n JSON locale files incrementally — only strings that actually changed since the last run are sent for translation.
The translator is fully configurable: use any LLM, any free translation service, or implement your own.
What it does
On each run transly scans your source locale directory, computes a SHA-256 hash of every string, compares it against a local cache, and translates only the keys that are new or changed. Translated strings are written to the target language directories and the cache is updated. If a batch fails mid-run, everything translated so far is already saved — just re-run to continue.
Why transly
- Only translates what changed, based on content hashes — not git history, not timestamps
- Cache is written after every chunk, so partial failures never lose work
- Translator backend is pluggable: LLM, free API, or your own function
- Works without any LLM config at all (falls back to a free translation service)
- Concurrent translation of multiple namespace × language pairs