---
title: Bulk Translations
feature: true
featureGroup: core
featureState: ga
description: Review and bulk-edit inline-translated entity fields across a whole type in a spreadsheet-like grid
date: 2026-06-18
tags:
  - translations
  - i18n
  - inline-translation
  - localization
---

# Bulk Translations

When you add a new language to a project after data already exists, every
inline-translated field on every entity starts out empty for that language and
falls back to the default. Opening hundreds of entities one by one to fill in
the missing translation is painful. The **Translations** settings module lets
you do it in one place.

## Where to find it

Open **Project Settings → Translations** (in the *Data* section). The module
lists every type in the project that has at least one inline-translated
property, together with a badge showing how many translation values are still
missing across all of its entities.

## Editing translations

Select a type to open its translation grid:

- Each **row** is an entity of that type.
- Each **column** is one inline-translated property in one language (for
  example `name · de`, `name · en`, `name · es`).
- Cells that are still empty are highlighted so you can spot gaps at a glance.
- Type into a cell, press **Tab** to move to the next one, and edit as many
  cells as you like.

Click **Save changes** to persist all your edits at once. Editing one language
never affects the others — the remaining languages of each field are preserved.
Saved values sync to every connected client automatically.

## Notes

- The available languages are the platform's supported locales; you do not need
  to configure them per project.
- Only inline-translated properties are shown here. Other field types are edited
  on the entity itself.

> **Coming soon:** machine translation to pre-fill a whole type into a target
> language, which you can then review and correct in the same grid.