Manually wrapping every string in t()? Stop. i18nmatic auto-detects translatable text—even for unwrapped text—wraps it in t(), adds imports, and generates translation keys with file paths. For React/Next.js + i18next. Internationalize in minutes.
✨ i18nmatic is exactly the kind of tool I wish I had when I had to retro-fit i18n into a large React project.
It automatically wraps strings in t(), adds imports, and even extracts keys into JSON with source file paths — all in minutes.
Super useful for teams trying to internationalize efficiently without wasting hours on repetitive tasks. Definitely keeping this in my toolbox. Great work!
🧠 i18nmatic solves a real pain point in i18n workflows.
The ability to auto-detect translatable text—even unwrapped ones—and wrap them in t() while generating structured JSON keys saves hours of manual work.
It’s especially helpful for scaling teams or refactoring legacy React apps.
Clean, focused, and works exactly as expected. Great job.
Report
Brand Context APIBrand context for AI agents. 50M+ brands, one API call.
Promoted
Maker
📌
👋 Hi Product Hunt community!
Internationalizing React & Next.js projects is incredibly powerful but can quickly turn into a tedious and repetitive task. I've personally spent hours manually wrapping texts in translation functions (`t()`) and extracting them into JSON files, wishing there was a better way.
So, I built **i18nmatic**—a CLI tool that fully automates this painful process. It transforms your codebase within minutes, freeing up valuable time for developers and helping you go global faster.
Would love your feedback, ideas, or even edge cases you’d like it to handle!
Report
I've literally spent hours wrapping t() around strings before. This looks super useful for teams coming in late to i18n.
Does it support template literals with variables too?
Yes! Template literals with variables are fully supported 🎉 i18nmatic automatically transforms them into dynamic translation keys using {{variable}} syntax. You can check out a live demo and code example in the README 👇
Report
Whoa, love this. I had to retroactively i18n a project last month and it was a nightmare 😩
Definitely trying this on our next sprint. Curious—does it play well with monorepos?
👋 Hi Product Hunt community!
Internationalizing React & Next.js projects is incredibly powerful but can quickly turn into a tedious and repetitive task. I've personally spent hours manually wrapping texts in translation functions (`t()`) and extracting them into JSON files, wishing there was a better way.
So, I built **i18nmatic**—a CLI tool that fully automates this painful process. It transforms your codebase within minutes, freeing up valuable time for developers and helping you go global faster.
Would love your feedback, ideas, or even edge cases you’d like it to handle!
I've literally spent hours wrapping t() around strings before. This looks super useful for teams coming in late to i18n.
Does it support template literals with variables too?
@devin_f_lab
Yes! Template literals with variables are fully supported 🎉 i18nmatic automatically transforms them into dynamic translation keys using {{variable}} syntax. You can check out a live demo and code example in the README 👇
Whoa, love this. I had to retroactively i18n a project last month and it was a nightmare 😩
Definitely trying this on our next sprint. Curious—does it play well with monorepos?
@habi
Yes! It works with nested folders and mono setups—just set your entry path properly