---
title: Translate a Next.js Site with AI | Smartcat
description: Translate your Next.js site with AI and review it in context. Install via the shared layout, loaded with the framework's Script component.
canonical: https://www.smartcat.com/integrations/nextjs/
language: en
updated: 2026-11-16
---

# Translate a Next.js Site with AI | Smartcat

## Translate your Next.js site with AI

Add the Smartcat website snippet to your Next.js project once, deploy it through your normal pipeline, and review translations in Smartcat before you publish a language.

- [Start free trial](https://smartcat.com/sign-up)

- [Book a demo](https://www.smartcat.com/book-a-demo/?nextjs)

## How to add Smartcat to Next.js

Create a Smartcat website project from your published Next.js URL and choose the target languages.

Install the generated Smartcat snippet through the shared layout, loaded with the framework's Script component.

Deploy the change and open the published site to confirm the snippet is present.

Review the translations in Smartcat’s visual editor and publish the languages that are ready.

## Add website translation to the Next.js application shell

Install the generated snippet in the application’s shared layout using Next.js’s supported script-loading mechanism. In an App Router project, the root layout defines the site-wide shell. The Script component’s strategy controls timing; afterInteractive is not equivalent to an early script in server-rendered head markup.

Validate the integration against hydration and client-side navigation. A product page reached through a Link should have the same language behavior as a direct load. Avoid mounting a second copy of the translator on every route change.

For an authenticated application with stateful UI, pluralization, and locale-aware formatting, use application i18n and a software-localization workflow. A website translation layer is not a substitute for translating message catalogs and application semantics.

## What changes for visitors, and what stays in Next.js

Website translation changes the published reading experience. It does not create translated source files, message catalogs, or locale builds in your Next.js repository.

## Review before a language goes live

Machine translation gives you a fast first draft. In Smartcat’s visual editor you see each translated string on the page, shorten headings that run long on mobile, and keep product and brand names consistent with a glossary. Assign a reviewer when a page needs approval, and publish only the languages that are ready.

## Frequently asked questions

### Should I use beforeInteractive for every translation script?

No universal strategy is prescribed. beforeInteractive runs from the root layout before normal client execution; afterInteractive runs later. The correct choice must preserve the generated snippet’s requirements and be validated against hydration.

### Can I edit translations before publishing?

Yes. Refine and confirm the wording in Smartcat’s visual editor, then publish the languages that are ready.

### What happens when I add a new page in Next.js?

New text follows the Smartcat project’s selected translation mode. Choose reviewed translations when every new page requires approval; automatic modes can translate newly encountered text. Neither mode changes your source content in Next.js.

Publish your Next.js site in more languages

Install the snippet once, review the translations in context, and publish the languages your audience needs. See all [website integrations](https://www.smartcat.com/integrations/category/website-translation/) or read how the [Website Translator](https://www.smartcat.com/website-translator/) works.

- [Start free trial](https://smartcat.com/sign-up)
