A project template lets you export the configuration of an existing project as a file, then reuse it to pre-fill a new project instead of setting up the same Organizational Unit, translation memories, glossaries, price list, and workflows from scratch every time.
​

💡 Who is this for? This guide is for Account Admins and Project Managers who need to reuse an existing project's settings when creating new projects within the wxrks platform.

A project template is a point-in-time snapshot of one project's settings, saved as a downloadable .json file. It only captures settings — files, tasks, translated content, and progress are never included, so importing a template always starts a brand-new, empty project.
​

This is different from Project Routing, which creates several projects at once — one per Organizational Unit — from a routing configuration you set up in advance. A project template works with any single existing project as its source and speeds up creating one new project at a time.

Open the project whose settings you want to reuse, click the Project Actions menu (the ☰ icon in the top-right corner of the Project Overview page), and select Export Project Template.

wxrks downloads a .json file named after the project (for example, My Project Name-template.json). Keep this file somewhere you can find it — you'll select it directly when creating the next project.

Exporting a template records:

Start creating a new project as usual. At the top of Step 1 (Configuration) — above the Organizational Unit field — click Import Project Template and select a previously exported .json file.

For the full walkthrough of every step and field in the creation wizard, see How to create a translation project in wxrks. This article focuses only on what the template import itself does.
​

Once the file loads, every setting it recorded pre-fills the matching field automatically — Organizational Unit, Contact person, source and target languages, translation memories, and glossaries:

...as well as the price list, further down the same step:

Once a template is loaded, a red trash-can button appears next to the file name (see the screenshot above). Click it to remove the template — this clears the pre-filled fields so you can import a different file or fill everything in manually. It has no effect on the original project the template was exported from.

Importing a template pre-fills the form — it doesn't lock it. Every field can still be changed before you create the project.
​

Changing the Organizational Unit after import has one important side effect: wxrks re-filters the imported translation memories, glossaries, and price list down to only the ones actually shared with the new Organizational Unit. Anything from the template that isn't available under the new unit is silently dropped from the selection rather than causing an error — worth double-checking those three fields after switching the Organizational Unit.
​

For example, if the imported template includes three translation memories but the new Organizational Unit only has access to one of them, only that one carries over — the other two are dropped without any warning.
​

Contact person, source and target languages, translation settings, the Quote Automation and Auto Task Placement toggles, and workflows are unaffected by an Organizational Unit change and carry over exactly as imported.