One project, more than one person
Collaborative Bible translation software — share the project, or sync the desktop.
Collaborative Bible translation software is how a team in more than one place keeps a single Scripture project. Paratext Send/Receive, Paratext Live, Scripture Forge, Bibledit, and V-MAST are the tools that search usually finds. Aquilla is one browser workspace for the people on the project. It does not sync with Paratext, run a live editing session, or work offline.
The direct answer
What is collaborative Bible translation software?
It is the shared project: more than one person, one text, without a pile of conflicting copies. Paratext documents Send/Receive and Paratext Live. Scripture Forge drafts in the browser beside Paratext. Bibledit syncs a team and can work offline. V-MAST is a browser for dispersed teams working in parallel. Aquilla does not do those sync jobs.
People searching for collaborative Bible translation software are choosing a sync method. A browser workspace is not Send/Receive, and it is not a live session.
The project-management page is the plan and the assignments. The notes page is a question on a verse. Use this page for how the team shares the file.
What the search is actually choosing
Collaborative software is a job list — not “a team exists.”
Searchers mix Send/Receive, a live session, offline merge, Paratext sync, and parallel work under a facilitator. Aquilla covers one browser project. It does not cover the rest.
| Job | Aquilla | Typical result for this search |
|---|
| Sync the project across computers, including by internet or USB | No — Aquilla does not do Paratext Send/Receive. | Yes — Paratext Send/Receive merges the team’s changes |
|---|
| Edit the same chapter live, with the team watching | No — Aquilla is not Paratext Live. | Yes — Paratext Live is the real-time session |
|---|
| Work offline and merge when the connection returns | No — Aquilla does not install for offline drafting. | Yes — Paratext and Bibledit are built for that |
|---|
| Draft in the browser and keep syncing to Paratext | No — no Paratext sync. USFM import and export only. | Yes — Scripture Forge syncs with the Paratext project |
|---|
| A dispersed team translates in parallel under a virtual facilitator | No — Aquilla does not assign parallel tasks or a facilitator. | Yes — V-MAST describes that browser workflow |
|---|
| People on the project open the same draft in a browser | Yes — one workspace, and Living Memory from decisions they authorize. | Yes — the shared project is the point of every tool above |
|---|
Keep the sync tool when the merge is the job
Collaboration is the shared project, not the task plan
Paratext’s project plan assigns who does which chapter. That is project management, on its own page. Collaborative Bible translation software is how the file stays one file when people are not in the same room. Aquilla does not assign the tasks. It also does not merge offline copies.
What stays in Paratext, Scripture Forge, Bibledit, or V-MAST
Paratext Send/Receive and Paratext Live are the desktop sync and the live session. Scripture Forge is the browser beside Paratext, including community checking. Bibledit syncs a team and can work offline. V-MAST is a browser for dispersed people working in parallel with a virtual facilitator. Keep the one your organization already trusts for that job.
What Aquilla covers
The people on the project open one browser workspace. Agents can propose a draft. A person authorizes meaning. Living Memory can apply a decision the team has already authorized to a later passage. Export USFM or USX when a consultant still checks in Paratext. There is no Send/Receive, no live session, and no offline merge.
Related, and not this page
Notes software is a question on a verse. Checking software is Basic Checks and translationCore. The workflow page is the quality stages. This page is only how a team shares the project.
Common questions
Collaborative Bible translation FAQ
What is collaborative Bible translation software?
It is the tool a team uses so more than one person can work on the same Scripture project without keeping separate copies. Paratext does that with Send/Receive and with Paratext Live. Scripture Forge does it in the browser beside Paratext. Bibledit syncs a team, including offline. V-MAST is a browser for dispersed teams working in parallel. Aquilla is one browser project for the people on it. It does not sync with Paratext and it does not work offline.
Does Aquilla replace Paratext Send/Receive?
No. Send/Receive is how a Paratext team merges changes over the internet or from a USB drive, and how conflicts get flagged. Aquilla does not send or receive a Paratext project, does not join the Paratext Registry, and does not merge an offline copy. Teams that already share work that way should keep it. Aquilla can import and export USFM or USX when the text needs to move.
Is Aquilla the same as Paratext Live?
No. Paratext Live is a real-time session: the team sees edits as they happen. Aquilla does not open that session. People on the project work in the browser workspace. That is not a claim that two people edit the same verse at the same moment with live cursors.
Can a remote team draft in the browser?
Yes, in the limited sense that the people on the project open the same workspace in a browser. Agents can propose a draft, and a person still authorizes meaning. Aquilla does not work offline, does not sync to Paratext in the background, and does not assign chapters to a virtual facilitator the way V-MAST describes.
Does collaboration include consultant notes and task assignments?
Not on this page. A question on a verse is Bible translation notes software. Who does which chapter, and whether the plan is on time, is Bible translation project management software. Aquilla does not replace consultant notes, and it does not assign tasks. This page is only the shared project.
How does this differ from Scripture Forge or Bibledit?
Scripture Forge drafts in the browser and syncs with Paratext, including community checking. Bibledit is free and open source, runs on many devices, and can work offline with a cloud sync. Aquilla does not sync with Paratext, is not an offline editor, and is not open source. It is a browser workspace where experts authorize drafts and Living Memory keeps decisions they have already approved.
How much does this cost in Aquilla?
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 one workspace. Keep the sync your team already trusts.
Open a Free plan and draft in the browser. Bible-translation teams and ETEN affiliates can contact us for team-plan access at no cost. Aquilla will not replace Send/Receive.