HomeSandboxShowcaseAppDocBlog
    • EnglishEnglish
      EN
    • русскийRussian
      RU
    • 日本語Japanese
      JA
    • françaisFrench
      FR
    • 한국어Korean
      KO
    • 中文Chinese
      ZH
    • españolSpanish
      ES
    • DeutschGerman
      DE
    • العربيةArabic
      AR
    • italianoItalian
      IT
    • British EnglishBritish English
      EN-GB
    • portuguêsPortuguese
      PT
    • हिन्दीHindi
      HI
    • TürkçeTurkish
      TR
    • polskiPolish
      PL
    • IndonesiaIndonesian
      ID
    • Tiếng ViệtVietnamese
      VI
    • українськаUkrainian
      UK
    /
    Filter docs by framework
    Alt+←
    Why Intlayer ?
    Get Started
    Concept
    • How Intlayer Works
    • Configuration
    • TestFillBuildWatchExtractLoginPushPullConfigurationListVersionEditorLiveDebugDoc ReviewDoc TranslateSDK
    • Visual Editor
    • CMS
    • CI/CD Integration
    • TranslationPluralEnumerationConditionGenderInsertionFileNestingMarkdownHTMLFunction Fetching
    • Per Locale File
    • Compiler
    • Auto Fill
    • Testing
    • Bundle Optimization
    Environment
    • Next.js 14 and App Router
      Next.js 15
      Next.js no locale path
      Next.js and Page Router
      Compiler
    • Tanstack Start Solid
    • Astro and React
      Astro and Svelte
      Astro and Vue
      Astro and Solid
      Astro and Preact
      Astro and Lit
      Astro and Vanilla JS
    • React Router v7
      React Router v7 (fs-routes)
      Compiler
    • Nuxt and Vue
    • Vite and Solid
    • SvelteKit
    • Vite and Preact
    • Vite and Vanilla JS
    • Vite and Lit
    • Angular 19 (Webpack)
      Analog
    • React CRA
    • React Native and Expo
    • Express.js
      NestJS
      Fastify
      Hono
      Adonis
    • Lynx and React
    Plugins
    • JSON
    • gettext (.po)
    VS Code Extension
    Agent
    • MCP Server
    • Agent skills
    Releases
    • v8
    • v7
    • v6
    Benchmark
    • Next.js
    • TanStack
    • Vue
    • Solid
    • Svelte
    Blog
    Ask a question
    1. Documentation
    2. Packages
    3. Next intlayer
    4. UseLocale
    Creation:2025-08-23Last update:2026-01-26
    Reference this doc to your favorite AI assistant
    ChatGPT
    Claude
    DeepSeek
    Google AI mode
    Gemini
    Perplexity
    Mistral
    Grok

    Ask your question and get a summary of the document by referencing this page and the AI provider of your choice

    Version History

    1. "Default `onLocaleChange` to `replace`"
      v8.0.01/26/2026
    2. "Added docs for `useLocale` hook with `onLocaleChange` option"
      v6.2.010/9/2025
    3. "Init history"
      v5.5.106/29/2025
    Edit this doc

    If you have an idea for improving this documentation, please feel free to contribute by submitting a pull request on GitHub.

    GitHub link to the documentation
    Copy

    Copy doc Markdown to clipboard

    Next.js Integration: useLocale Hook Documentation for next-intlayer

    This section offers detailed documentation on the useLocale hook tailored for Next.js applications within the next-intlayer library. It is designed to handle locale changes and routing efficiently.

    Importing useLocale in Next.js

    To utilize the useLocale hook in your Next.js application, import it as shown below:

    javascript
    Copy code

    Copy the code to the clipboard

    import { useLocale } from "next-intlayer"; // Used for managing locales and routing in Next.js

    Usage

    Here’s how to implement the useLocale hook within a Next.js component:

    src/components/LocaleSwitcher.tsx
    Copy code

    Copy the code to the clipboard

    "use client";
    
    import type { FC } from "react";
    import { Locales } from "intlayer";
    import { useLocale } from "next-intlayer";
    
    const LocaleSwitcher: FC = () => {
      const { locale, defaultLocale, availableLocales, setLocale } = useLocale();
    
      return (
        <div>
          <h1>Current Locale: {locale}</h1>
          <p>Default Locale: {defaultLocale}</p>
          <select value={locale} onChange={(e) => setLocale(e.target.value)}>
            {availableLocales.map((loc) => (
              <option key={loc} value={loc}>
                {loc}
              </option>
            ))}
          </select>
        </div>
      );
    };

    Parameters

    The useLocale hook accepts the following parameters:

    • onLocaleChange: A string that determines how the URL should be updated when the locale changes. It can be "replace", "push" or "none".

      Let's take an example:

      1. You are on /fr/home
      2. You navigate to /fr/about
      3. You change the locale to /es/about
      4. You click the browser's "back" button

      The behavior will differ based on the onLocaleChange value:

      • "replace" (default) : Replaces the current URL with the new localized URL, and set the cookie. -> The "back" button will go to /es/home
      • "push": Adds the new localized URL to browser history, and set the cookie. -> The "back" button will go to /fr/about
      • "none": Only updates the locale in the client context, and set the cookie, without changing the URL. -> The "back" button will go to /fr/home
      • (locale) => void: Set the cookie and trigger a custom function that will be called when the locale changes.

        The undefined option is the default behavior as we recommend to use the Link component to navigate to the new locale. Example:

        tsx
        Copy code

        Copy the code to the clipboard

        <Link href="/es/about" replace>  About</Link>

    Return Values

    When you invoke the useLocale hook, it returns an object containing the following properties:

    • locale: The current locale as set in the React context.
    • defaultLocale: The primary locale defined in the configuration.
    • availableLocales: A list of all locales available as defined in the configuration.
    • setLocale: A function to change the application's locale and update the URL accordingly. It takes care of prefix rules, whether to add the locale to the path or not based on configuration. Utilizes useRouter from next/navigation for navigation functions like push and refresh.
    • pathWithoutLocale: A computed property that returns the path without the locale. It is useful for comparing URLs. For example, if the current locale is fr, and the url fr/my_path, the path without locale is /my_path. Utilizes usePathname from next/navigation to get the current path.

    Conclusion

    The useLocale hook from next-intlayer is a crucial tool for managing locales in Next.js applications. It offers an integrated approach to adapt your application for multiple locales by handling locale storage, state management, and URL modifications seamlessly.

    Why Intlayer ?
    Alt+→

    In this page

      Discussions are anonymous and regularly reviewed to address common issues. Feel free to share feature ideas, feedback on the documentation, or anything related to Intlayer, we use this input to shape our roadmap and improve the product.

      import { useLocale } from "next-intlayer"; // Used for managing locales and routing in Next.js
      <Link href="/es/about" replace>  About</Link>