Bridging the gap between #translation and #development. By the creators of i18next… #ContinuousLocalization #i18n #l10n #t9n #xl8 #g11n #m17n

Joined May 2016
533 Photos and videos
Pinned Tweet
12 minutes. The entire Locize product, end-to-end. We don't do sales calls — so this is exactly what we'd show you on one. 📺 youtu.be/lCuHSZvSiVg📄 locize.com/blog/what-is-loci…
1
1
45
Jun 12
i18next AND inlang. Not either/or. npx i18next-cli init --inlang Sherlock, Fink & Paraglide now work on your existing i18next JSON. Nothing migrates. 7 interop bugs found, 7 fixed within hours, together with @samuelstroschei 🤝 locize.com/blog/inlang-inter…
1
2
118
May 27
10 years of Locize 🎂 Around this time in 2016, locize.com launched as a small backend for i18next. It still does that today. Just quite a bit more. Same workflow. Same Swiss-made platform. Same co-founders. Ten more years to go. 🔗 locize.com/blog/10-years-of-…
2
2
29
May 20
🚀 Nuxt 4 @nuxtjs/i18n Locize: step-by-step walkthrough is live. Build-time sync via locize-cli, Nitro-safe, optional saveMissing in-context editor (locize 4.1 now ships a vue-i18n implementation). 📝 locize.com/blog/nuxt-i18n 💻 github.com/locize/locize-nux…
30
May 19
Moving a Remix app to React Router v7? remix-i18next (by @sergiodxa) targets RR v7 framework mode. New walkthrough covers the middleware-based locale detection, SSR-bundled translations, client-side CDN lazy-load, saveMissing, and the in-context editor. locize.com/blog/react-router…
1
4
149
Apr 13
i18next in Production: Managing Translations at Scale This post covers the practical problems that appear when managing translations at scale, and the i18next ecosystem patterns that solve them. locize.com/blog/i18next-in-p…
1
1
50
Apr 10
next-intl vs next-i18next: Choosing the Right i18n Library for Next.js This post compares them on the things that matter for a real project: how translations are loaded, how they integrate with your stack, and what workflows they enable. locize.com/blog/next-intl-vs…
1
1
41
How to Set Up Automatic Translation with i18next This guide shows how to eliminate all of those manual steps using i18next's saveMissing feature and Locize's automatic translation workflow. The result: you write code, and translations appear. locize.com/blog/automatic-tr…
1
1
45
Alternatives Compared: How We Stack Up Choosing a TMS is a decision that stays with your project for years. This post compares us with the most common alternatives, focusing on what actually matters... locize.com/blog/locize-alter…
1
1
33
If you're building with an AI coding assistant... Cursor, Claude Code, GitHub Copilot, or similar... you can set up a complete localization workflow in minutes. This guide shows the shortest path from zero to live translations using i18next and Locize. locize.com/blog/ai-quickstar…
1
1
115
I added a console notice to i18next (15M weekly downloads) and then removed it. Here's the honest story of why we did it, what the data showed, and why we reversed the decision: locize.com/blog/i18next-supp…
1
3
104
Mar 28
We added a console notice to i18next (15M weekly downloads) and then removed it. Here's the honest story of why we did it, what the data showed, and why we reversed the decision: locize.com/blog/i18next-supp…
1
20
Mar 25
The Locize MCP server is live 🎉 Connect Claude, Cursor or VS Code directly to your translation projects. → "Find missing German translations" → "Publish the production version" → "Create a feature branch, merge when ready" 22 tools. 60 second setup. locize.com/blog/mcp-server
2
59
next-i18next v16 is out 🎉 First-class App Router suppor, Server Components, Client Components, Edge proxy, while keeping full Pages Router compatibility. One package, every Next.js i18n scenario. Full guide → locize.com/blog/next-i18next…
1
3
104
Internationalizing a React app doesn't have to be a "tedious weekend project" anymore. 🚀 The new i18next-cli instrument command turns hours of manual labor into minutes of automation Go from zero i18n to global-ready in record time. Read the full guide: locize.com/blog/i18next-cli-…
2
2
40
Big news for the i18next community! 🚀 We’re making it official: Locize now has a Free plan. 🆓 ✅ Perfect for hobbyists & small OSS projects ✅ Supports the i18next maintainers Start small, scale up only when you need to. Read more about: dev.to/adrai/finally-a-free-…
1
2
66
Feb 21
Predictable pricing has arrived at Locize! 📈 We’ve launched Fixed Plans a Forever Free tier to give developers and teams more choice. 🆕 Fixed Plans 🆓 Forever Free Plan 🔄 Stay Flexible 🚫 Zero Sales Reps Check out the new plans: locize.com/blog/new-pricing-…
1
1
36
Don't let your translations disappear in a tunnel! 🚇❌ Build resilient, offline-first apps by combining the agility of the CDN with the reliability of i18next chained backends. Check it out: locize.com/blog/building-rob…
1
1
71
Jan 26
Is self-hosting your localization actually saving you money? Or are you just paying for it in senior developer hours...? locize.com/blog/diy-localiza…
1
1
52
Jan 19
Locize is going back to its roots. 🌱 We’ve officially launched the all-new locize.com — and it’s more than just a redesign. We stripped the marketing fluff to double down on what matters: technical excellence for developers. 🧵 (1/4)
1
1
1
46
Jan 19
The new screenshots on the site aren’t just for show. They reflect a major UI/UX overhaul of the Locize App itself. ✅ Cleaner, high-contrast interface ✅ Faster loading and save times ✅ Fewer clicks for your core tasks What you see is what you get. (3/4)
1
1
21
Jan 19
From our foundation with i18next to the platform we are today, we believe localization should be an invisible, high-performance part of your tech stack. 🌍 No sales decks. No noise. Just the tools you need to go global. Read the full story: locize.com/blog/back-to-root… (4/4)
1
13