Living Memory, not a TMX file
When a translator authorizes a rendering, later drafts can use that decision. That is project memory. It is not a portable TMX, TBX, or XLIFF package, and Aquilla does not open those files.
Scripture consistency
Translation memory software for Bible translation remembers how the team already rendered a term so later chapters do not drift. Aquilla does that with Living Memory from decisions translators authorize. It is not Paratext’s Biblical Terms tool, and it does not import TMX from Trados or memoQ.
The direct answer
It is a record of approved renderings so “covenant,” a proper name, or a repeated phrase stays consistent from Genesis to the last book you draft. Paratext does that with translation memory and Biblical Terms. Aquilla does it with Living Memory in a browser workspace. The linguist still owns the term.
Searchers comparing translation memory software for Bible translation usually land on three different products. Paratext’s desktop suite tracks Biblical Terms and previous verses. General CAT tools store TMX segments from agency jobs. A few Scripture-specific editors remember sentence-level decisions inside a book project.
Aquilla is the third job, with a hard boundary: Living Memory compounds authorized decisions; it does not replace Biblical Terms, and it does not open TMX.
What the search is actually choosing
The useful split is Scripture consistency versus CAT interchange. Aquilla covers the first and is explicit about the second.
| Job | Aquilla | Typical result for this search |
|---|---|---|
| Remember approved renderings across later books | Yes — Living Memory learns from decisions you already authorized. | Yes — Paratext translation memory and Biblical Terms renderings |
| Paratext Biblical Terms tool | No — keep biblical-terms checking in Paratext if that is your suite. | Yes — the desktop Biblical Terms window and glossary |
| Import TMX from Trados, memoQ, or OmegaT | No — Aquilla does not import TMX, TBX, or XLIFF packages. | Yes — that is how general CAT translation memory moves between tools |
| Segment fuzzy match on previous verses | No exact-segment TM. Living Memory is project context from approved work. | Yes — CAT tools and some Scripture editors match prior segments |
| Learn without a completed New Testament | Yes — memory accumulates from the work you approve as you go. | Often a term list plus TM built from already-translated books |
| Share memory with the rest of the team | Yes — one project memory in the browser workspace. | Yes — Send/Receive or a shared TMX / termbase |
When a translator authorizes a rendering, later drafts can use that decision. That is project memory. It is not a portable TMX, TBX, or XLIFF package, and Aquilla does not open those files.
Paratext’s Biblical Terms tool tracks covenant, Lord, Spirit, and names across the whole Bible. Aquilla does not replace that desktop checking suite. If consultants still run Biblical Terms in Paratext, export USFM and keep that check there.
General translation memory software — Trados, memoQ, OmegaT — remembers segments from client jobs. Bible translation memory is consistency across books and years. Aquilla is the Scripture workspace job, not an agency CAT.
Some AI drafting tools train on a finished New Testament before they draft later books. Living Memory does not wait for that. It learns from the decisions you approve on the books you are actually translating.
Oral drafts and written text can share the same project memory so a term decided in a written chapter is available when the next draft is spoken. That is one workspace, not a separate oral suite.
Memory that copies a wrong term is worse than no memory. Aquilla only compounds decisions translators have already approved. Agents propose; the team still owns the glossary.
Scripture memory vs CAT memory
The professional translation tools page is the CAT editor job: Living Memory in a browser workspace, no Trados or memoQ package import. This page is the Bible-specific question those CAT results do not answer — how key terms stay consistent across books of Scripture.
If you need to open an agency TMX, stay on a CAT tool. If you need Biblical Terms, versification, or parallel passages, keep Paratext. If you need a Scripture workspace that learns from the renderings you already approved, that is Aquilla.
Common questions
It is software that remembers how a team already rendered a phrase, a key term, or a name so later books stay consistent. In Paratext that job is translation memory plus the Biblical Terms tool. In general CAT tools it is a TMX file of previous segments. Aquilla does the Scripture consistency job with Living Memory: it learns from renderings the team has already authorized, in the same browser workspace as the draft.
No. Paratext stores previous translations and runs Biblical Terms, wordlists, and parallel passages as a desktop checking suite. Aquilla is a browser workspace. Living Memory applies approved decisions to later drafts. It does not implement Send/Receive, and it does not replace the Biblical Terms tool. If that desktop check is still required, export USFM and run it in Paratext.
No. Biblical Terms is Paratext’s desktop list of key theological words, names, and places. Aquilla does not ship that tool. Teams that still need biblical-terms, versification, or parallel-passage checks should keep that work in Paratext.
No. Aquilla does not import TMX, TBX, or XLIFF, and it does not open Trados Studio or memoQ packages. Scripture teams move USFM/USX when a consultant or archive still needs those files. If the job is exchanging CAT memory with an agency, stay on a CAT tool.
CAT translation memory matches previous segments from client jobs, usually as TMX. Bible translation memory is consistency of key terms and phrasing across Scripture books. The professional translation tools page covers the CAT editor job. This page is the Scripture job. Aquilla’s Living Memory is the second kind, inside a Bible translation workspace.
No. Some AI drafting tools train on a completed New Testament, then draft later books into Paratext. Living Memory learns from the decisions you approve as you work, including on projects that do not yet have a finished testament.
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.
Start on the Free plan. Bible-translation teams and ETEN affiliates can contact us to activate team-plan access. Keep Biblical Terms in Paratext if that check is still required.