Skip to content
Locize
LoginRegister

Which integration option should I use?

Choosing the right integration depends on your project type, technical needs, and how much control you want. Here’s a quick guide:

1. For Static Websites

  • Recommended: locizify
  • Why: Easiest setup, minimal code changes, and even non-developers can use it. Great for marketing sites, landing pages, and simple web projects.

2. For Web, Mobile, Desktop, or Server Apps

  • Recommended: i18next
  • Why: Maximum flexibility and control. Supports advanced features like plurals, interpolation, context, and more. Works with all major frameworks (see supported frameworks, plugins).

3. For Automation & CI/CD

  • Recommended: Locize CLI
  • Why: Automate translation sync, upload, and download tasks in your build or deployment pipelines. Perfect for continuous localization workflows.

4. For Custom or Advanced Integrations

  • Recommended: Locize API
  • Why: Gives you full programmatic access. Build your own workflows, automation, or integrations beyond standard use cases.

5. For CI/CD Pipelines with GitHub Actions

6. For AI Coding Assistants (Claude, Cursor, VS Code)

  • Recommended: Locize MCP Server
  • Why: Manage translations directly from your AI assistant: check coverage, report new keys, publish versions, manage branches. 22 tools covering the full translation lifecycle.

Summary:

  • Use locizify for static sites and simplicity
  • Use i18next for apps and advanced features
  • Use the CLI for automation and CI/CD
  • Use GitHub Actions for CI/CD pipeline integration
  • Use the MCP Server for AI coding assistant integration
  • Use the API for custom solutions

Still unsure? Contact us and we’ll help you choose the best option for your needs!