---
title: "Publish a language"
description: "Make a reviewed language available to customers and restore an earlier version when needed."
canonical_url: "https://docs.linguana.dev/docs/use-linguana/publish-language"
markdown_url: "https://docs.linguana.dev/docs/use-linguana/publish-language.md"
x_farming_labs_generated_preamble: true
---

# Publish a language
URL: /docs/use-linguana/publish-language
LLM index: /llms.txt
Description: Make a reviewed language available to customers and restore an earlier version when needed.

# Publish a language

Once a language has been reviewed, publish it from the dashboard. You can restore an earlier version without losing the newer one.

## Development and production

Development builds can publish development catalogs when the Vite plugin’s `translation` option explicitly enables it with a token, cap, and `publish: "development"`. A plain upload does not translate or publish. The dashboard’s **Publish ready catalog** action currently targets production.

## Publish a language

1. Open **Releases** for your project.
2. Confirm **Ready to publish** shows the expected language and content.
3. Choose **Publish ready catalog**.
4. Confirm the production target and choose **Publish catalog**. Use a catalog built for production and a runtime configured for production; do not assume a development catalog can be served in another environment.

New catalog requests use the published release pointer. Browser or CDN caches and an already loaded runtime can retain the prior wording until it reloads. The previous immutable version remains available.

## Restore an earlier version

In **Release history**, find the version you want, choose **Restore**, and confirm. This changes what your application loads without deleting newer versions.

<ExpectedResult>
New language requests load the selected version. Existing versions remain available for inspection or restoration.
</ExpectedResult>

## If a language is not ready

Finish the translation run, translate missing strings, or resolve its review list first. Accepted strings and an empty review queue alone do not prove a complete catalog is ready. If your application still shows old text, check its project, environment, language, and API settings.

## Failure and next

For loading problems, read [Show translated content](/docs/build-with-code/show-translated-content) and [Catalog runtime troubleshooting](/docs/troubleshooting/catalog-runtime).

## Sitemap

See the full [sitemap](/sitemap.md) for all pages.
Docs-scoped sitemap: [/docs/sitemap.md](/docs/sitemap.md).
Well-known sitemap: [/.well-known/sitemap.md](/.well-known/sitemap.md).