# gt-next: General Translation Next.js SDK: Standalone i18n
URL: https://generaltranslation.com/en-GB/docs/next/concepts/stand-alone.mdx
---
title: Standalone i18n
description: How to use gt-react as a standalone i18n library
---

{/* AUTO-GENERATED: Do not edit directly. Edit the template in content/docs-templates/ instead. */}


## Overview

`gt-next` has feature parity with many other i18n libraries.
This means you can use `gt-next` as a standalone i18n library without using the General Translation platform.

To do this, do not provide any environment variables such as `GT_API_KEY` or `GT_PROJECT_ID`.

See our [migration guide](/docs/next/guides/migration) for more information on migrating from another i18n library to `gt-next`.

## Trade-offs

Using `gt-next` as a standalone i18n library has some trade-offs.

### Manual translation

You will need to translate your app manually. If you use our platform, we automatically translate your app for you.

If your project only uses [dictionaries](/docs/next/guides/dictionaries) with the `useTranslations` function,
you'll need to translate your dictionaries manually, as you would with any other i18n library.

Make sure you load your translated dictionaries with the [`loadDictionary`](/docs/next/api/config/load-dictionary) function.

***

### Manual string translation

If your project uses inline translations with the [`<T>`](/docs/next/guides/t) component
or the [`useGT`](/docs/next/guides/strings) functions,
you&#39;ll also need to translate your strings manually.

Since there are no keys for inline translations, the CLI tool includes a command: [`gt generate`](/docs/cli/generate)
which automatically generates template files for your project. You&#39;ll just need to edit the template files with your translations for each language.

Make sure you load your translated strings with the [`loadTranslations`](/docs/next/api/config/load-translations) function.

### No development translations