# Translating a submission

Read an answer written in a language you do not speak, translated in place with AI credits.

## Translating a submission

A multilingual form collects answers in the respondent's language. Translate a response into yours without leaving the submissions table.

<h2 id="why">Why you would</h2>

<p>
  A <a href="/building-forms/translating-form-content">multilingual form</a> lets each respondent answer in their own language, which is the
  point — but it means the free-text answers arrive in whatever language they wrote. Translating a submission renders those answers in your
  language so you can actually read the response.
</p>

<h2 id="how">Translating one</h2>

<p>
  In the submissions table, open the <strong>Actions</strong> menu on a row and choose <strong>Translate submission</strong>. While it runs
  the row shows <strong>Translating submission</strong>; when it finishes you get <strong>Submission translated</strong>.
</p>

<p>
  After that the row carries a toggle: <strong>Show original</strong> and <strong>Show translation</strong>. The original answer is never
  overwritten — the translation is stored alongside it, and you can switch back at any time.
</p>

<h2 id="target-language">Which language it translates into</h2>

<p>
  You are not asked to pick one. formbase translates into your workspace's notification language, and falls back to the language you are
  using formbase in when that is not set. Change the workspace notification language to change the target.
</p>

<h2 id="what-gets-translated">What gets translated</h2>

<ul>
  <li>
    <strong>Text answers only.</strong> Written answers are translated. Values with no language in them are left exactly as they are: dates,
    times, numbers, ratings, linear scales, email addresses, phone numbers, website URLs, scheduled appointments, uploaded files, signatures
    and payments.
  </li>
  <li>
    <strong>Answers, not questions.</strong> Question titles come from the form, which already has its own translations.
  </li>
  <li>
    A submission with no text answers reports <strong>No text answers to translate</strong> and spends nothing.
  </li>
  <li>
    A submission already in your target language reports <strong>Submission is already in the target language</strong> and spends nothing.
  </li>
</ul>

<h2 id="credits">What it costs</h2>

<p>
  Translation runs on <a href="/ai/ai-credits-usage">AI credits</a>, using the fast, inexpensive Haiku model. Your workspace needs a credit
  balance above zero; with none, formbase declines with <em>Not enough AI credits to translate this submission</em> rather than translating
  and billing you anyway.
</p>

> 💡 **Translating twice is free**
> <p>
>     A translation is cached against the exact content it was made from. Translating the same submission again returns the stored translation
>     and spends nothing. It is only re-translated — and only then charged again — if the submission itself changes, for instance when a
>     respondent <a href="/submissions-analytics/edit-after-submit">edits their answers</a> afterwards.
>   </p>

<h2 id="lifecycle">How long a translation lasts</h2>

<p>
  A translation belongs to its submission. Deleting the submission deletes its translation, and so does deleting the form. Nothing extra is
  kept behind, and <a href="/submissions-analytics/submission-retention">retention</a> applies to translations exactly as it does to the
  answers they came from.
</p>

<h2 id="next-steps">Next steps</h2>
<div class="not-prose grid gap-3 sm:grid-cols-2">
  - [Submission inbox](/submissions-analytics/submission-inbox) — Read and manage responses
  - [AI credits & usage](/ai/ai-credits-usage) — What each AI action costs
  - [Translating form content](/building-forms/translating-form-content) — Offer the form in several languages
  - [Exports](/submissions-analytics/exports) — Download responses as CSV or Excel
</div>