Inspection, not a second Bible
A back translation restates the draft in a language the consultant knows. It is often more literal than the translation itself. It is not the Scripture you publish.
Consultant inspection
Bible back translation software lets a consultant see what a draft says in a language they can read. Aquilla shows a back translation as you work. It is not Paratext’s interlinearizer, and it does not replace an independent back translator.
The direct answer
It produces a gloss of the draft in the consultant’s language so meaning can be checked by someone who does not speak the target language fluently. Paratext keeps that gloss in a separate project. Render can use audio. Aquilla shows a back translation while you draft, as an inspection aid. The gloss is not publishable Scripture, and the consultant check still happens with people.
Paratext’s training manual treats back translation as preparation for a consultant check. One module is a free back translation, typed by someone who was not the translator. The next is a word-for-word gloss from the interlinearizer. Render’s consultant check can play a passage or segment back translation beside the target-language recording when those stages are enabled.
Aquilla fills one box on that list: a back translation you can read as you work, next to real-time checks, so a drift in meaning is visible earlier. It does not create the separate Paratext project, it does not learn a word-for-word interlinear, and it does not staff the consultant.
What the search is actually choosing
Searchers mix a consultant gloss, Paratext’s interlinearizer, and an oral audio back translation. Aquilla covers the inspection aid and is explicit about the rest.
| Job | Aquilla | Typical result for this search |
|---|---|---|
| Show a gloss a consultant can read | Yes — back translation as you work, so you can inspect a draft. | A separate Paratext back-translation project, often in English |
| Word-for-word interlinear that learns glosses | No — Aquilla is not the Paratext interlinearizer. | Yes — Paratext’s interlinearizer, in its own project |
| An independent person who did not draft the text | No — Aquilla does not assign a back translator. | Paratext training prefers someone who was not the translator |
| Audio passage or segment back translation | No — not Render’s consultant-check audio tabs. | Yes — Render, when passage or segment back translation is turned on |
| The consultant check itself | No — Aquilla does not replace the consultant or the meeting. | A consultant reviews meaning with the team |
| Publish the back translation as Scripture | No — a back translation is an inspection aid, not a finished text. | Also no — a back translation is not meant to be natural or publishable |
A back translation restates the draft in a language the consultant knows. It is often more literal than the translation itself. It is not the Scripture you publish.
Aquilla can show a back translation while you draft, alongside real-time checks, so a meaning problem is visible before a consultant meeting. That is an aid. It is not a completed consultant check.
Paratext’s training manual prefers a person who was not the translator, working without peeking at the source, so the gloss reports what the text says rather than what the drafter meant. Aquilla does not recruit that person.
Keep the interlinearizer in Paratext if the project depends on it. Keep Render’s audio back-translation stages if the project is oral and those tabs are how the consultant listens. Export USFM/USX from Aquilla when that handoff is required.
Software vs the stage
Back translation sits in the quality sequence after a draft exists and before or during consultant review. The workflow page explains that stage. This page stops at the software boundary: what Aquilla shows while you draft, and what Paratext and Render still do when a project depends on them.
If you need the stage described, use the workflow. If you need to know whether Aquilla is the interlinearizer, use this page.
Common questions
It is software that helps a consultant see what a target-language draft says, usually by producing a gloss in a language they read. Paratext does this in a separate project, either as a free back translation or as a word-for-word gloss from the interlinearizer. Render can play an audio back translation during consultant check. Aquilla shows a back translation as you work so you can inspect a draft. It does not replace those tools or the consultant.
No. A back translation is a window onto the draft, often literal, in the consultant’s language. It is not meant to be natural, and it is not the Scripture you publish. The translation is the text or recording the team is preparing for the language community.
No. Paratext’s interlinearizer builds a word-for-word back translation and learns from earlier glosses inside a Paratext project. Aquilla does not ship that tool, does not join Paratext Registry, and does not implement Send/Receive. If the consultant still wants the interlinearizer, keep that project in Paratext and export USFM/USX when you need to move a draft.
Aquilla can show a back translation as you draft so you can inspect meaning. That generated gloss is not a substitute for an independent human back translator, and it is not a consultant check. Someone who did not draft the text may still need to prepare the gloss your consultant trusts. Agents propose; people decide what the consultant sees.
No. Choosing a back translator and assigning a consultant are organization jobs. Aquilla does not recruit either person and does not run the consultant meeting.
The workflow page describes back translation as a quality stage: a person writes a gloss so the consultant can check meaning. This page is the software question — which tool prepares that gloss, and which parts Aquilla actually does. Use the workflow page for the stage. Use this page to see the Paratext, Render, and Aquilla boundary.
No. Render’s consultant check can play a passage or segment back translation beside the target-language recording. Aquilla does not provide those audio tabs. Text and audio can share a workspace; that is not the same as Render’s back-translation stages.
Anyone can start on the Free plan with a weekly allowance of AI assistance. Bible-translation teams and ETEN affiliates get team-plan access at no cost — contact us to activate your organization’s workspace.
Open a Free plan and read a back translation as you draft. Bible-translation teams and ETEN affiliates can contact us for team-plan access at no cost. Aquilla will not assign your consultant or replace the Paratext interlinearizer.