# Verbaly > i18n that feels like no setup: you write natural text in your code and the compiler extracts it into stable keys, type-safe params and per-locale catalogs. The runtime is 3.35 KB gzip with zero dependencies, and the whole cycle (init, write, extract, translate, review, check, render) lives in one tool. Current version: 0.86.2 (npm: verbaly, MIT). Quick start: `npx verbaly init`, add the bundler plugin or framework integration (@verbaly/vite, @verbaly/react, @verbaly/vue, @verbaly/svelte, @verbaly/sveltekit, @verbaly/nuxt, @verbaly/next, @verbaly/astro, @verbaly/unplugin), write ``t`Hello ${name}` `` and run `npx verbaly extract`. Every build lists missing and broken translations (a dropped placeholder, a lost tag, a flattened plural block) and still finishes; `npx verbaly check` is the strict control, failing CI while any remain. Machine translations stay drafts until a human reviews them. For coding agents: the MCP server `@verbaly/mcp` exposes the cycle as tools, in the order an agent meets a project (verbaly_init, verbaly_doctor, verbaly_wrap, verbaly_extract, verbaly_status, verbaly_missing, verbaly_translate, verbaly_write_drafts, verbaly_drafts), each answering with structured output as well as text (`claude mcp add verbaly -- npx -y @verbaly/mcp`). It also serves verbaly://config and verbaly://catalog/{locale} as resources, which is the only way to read what a message says: every tool works in keys and counts. An installable Agent Skill lives in the repository under skills/verbaly, and an agent that looks for skills on this site finds it in https://verbaly.dev/.well-known/agent-skills/index.json. Both are documented at https://verbaly.dev/docs/guide/agents. Machine translations are always drafts and no agent tool can approve them. Every page below is plain Markdown, at the address of its HTML page plus .md, and https://verbaly.dev/llms-full.txt holds the whole documentation in one file. ## How it compares An honest look against the tools you'd otherwise reach for. It shows where Verbaly wins, and where the others are fine too. Checked against each tool's own documentation in November 2026 (i18next 27, Lingui 6, Paraglide 3). Sizes are min + gzip of what an app imports, with React left out. | Feature | Verbaly | i18next | Lingui | Paraglide | | --- | --- | --- | --- | --- | | Type-safe keys & params | Inferred from your text | Built in, from a declaration file | Text in code, no keys to mistype | A typed function per message | | Runtime size (gzip) | 3.35 KB, zero deps (6.17 with DOM + urls) | 15.5 KB (22.1 with React) | 2.3 KB (4.4 with React) | compiled, no shared runtime | | Key maintenance | None, auto-extracted | Written by hand, synced by its CLI | Extract → compile step | By hand | | Dynamic / CMS content | Real runtime path | Yes | Yes | Best with keys known at build time | | Plain HTML (no framework) | DOM interpreter | With a jQuery plugin | Not covered | Not covered | | Missing translations | Fails CI, every build lists it | A CLI command, for CI | CI step | inlang check, in CI | | Broken translations | Fails CI, every build lists it | CLI lint, a warning by default | Syntax errors only | inlang check, in CI | | Catalog format | Plain JSON | JSON | PO, JSON or CSV | inlang format, others by plugin | | Coding agents | MCP server + skill | Skill, hosted MCP (Locize) | Skills + plugin | Not covered | | Maturity & ecosystem | Pre-1.0: the API can still change | Proven at scale, modules for everything | Stable, standard PO for translators | Stable, with the inlang tools | ## Start - [What is Verbaly?](https://verbaly.dev/docs/init/what-is.md): The idea in five minutes: write text in your code, the compiler does the rest - [Getting started](https://verbaly.dev/docs/init/start.md): Install, init and first translated text - [Migrate to Verbaly](https://verbaly.dev/docs/guide/migrate.md): Migrate from i18next step by step - [Packages](https://verbaly.dev/docs/init/packages.md): Every package in one page: runtime, CLI, bundler plugins, framework integrations, the MCP server and the local review server ## Integrations - [Plain HTML](https://verbaly.dev/docs/frameworks/dom.md): Plain HTML with data-verbaly attributes, no framework - [Vite](https://verbaly.dev/docs/frameworks/vite.md): The Vite plugin: live extraction, the verbaly/app module, build report - [React](https://verbaly.dev/docs/frameworks/react.md): React hooks and Trans, plus Next.js App Router at #next - [Next.js](https://verbaly.dev/docs/frameworks/react.md#next): React hooks and Trans, plus Next.js App Router at #next - [Vue](https://verbaly.dev/docs/frameworks/vue.md): Vue composables and Trans, plus Nuxt at #nuxt - [Nuxt](https://verbaly.dev/docs/frameworks/vue.md#nuxt): Vue composables and Trans, plus Nuxt at #nuxt - [Svelte](https://verbaly.dev/docs/frameworks/svelte.md): Svelte 5 stores and Trans, plus SvelteKit at #sveltekit - [SvelteKit](https://verbaly.dev/docs/frameworks/svelte.md#sveltekit): Svelte 5 stores and Trans, plus SvelteKit at #sveltekit - [Astro](https://verbaly.dev/docs/frameworks/astro.md): Astro integration: extraction from .astro files and per-locale SSG ## Guides - [Keys and catalogs](https://verbaly.dev/docs/guide/keys.md): Keys and catalogs: every way to name a message, keys typed in every t, flat and nested catalogs, which languages you have - [Message format](https://verbaly.dev/docs/guide/format.md): Message syntax: params, formats, plurals, rich text, escapes, ICU - [URL strategy](https://verbaly.dev/docs/guide/urls.md): Should the language live in the URL: the two strategies, what each costs in SEO, and what works on a SPA, a server and a static site - [Server-side](https://verbaly.dev/docs/guide/server.md): SSR and SSG: per-request locale, hydration without flashes, render - [Testing](https://verbaly.dev/docs/guide/testing.md): Testing: build an instance with inline messages, assert, switch language - [Translators & TMS](https://verbaly.dev/docs/guide/translators.md): The human loop: export/import (XLIFF, CSV, PO), machine translation with review, mobile delivery - [Coding agents](https://verbaly.dev/docs/guide/agents.md): The agent channel: the MCP server with its tools and resources, the installable Agent Skill, and this index - [Studio](https://verbaly.dev/docs/guide/studio.md): The local review server: read every catalog, write a translation back, approve machine drafts - [When something breaks](https://verbaly.dev/docs/guide/troubleshooting.md): When something breaks: the command not found, a language you never asked for, a broken translation, stale types ## Reference - [Runtime API](https://verbaly.dev/docs/reference/api.md): Runtime API: createVerbaly, t, locale helpers, bindDom - [Configuration](https://verbaly.dev/docs/reference/config.md): Every option of verbaly.config, plus the render and translate sections - [CLI](https://verbaly.dev/docs/reference/cli.md): Every CLI command and flag, grouped by the stage of the cycle - [Devtools](https://verbaly.dev/docs/reference/devtools.md): The opt-in devtools overlay and the onResolve hook ## More - [Changelog](https://verbaly.dev/changelog): what each release added - [GitHub](https://github.com/verbaly-i18n/verbaly): source, issues and full release notes - [npm](https://www.npmjs.com/package/verbaly): the published package