# Common Works Registration (CWR) validator and generator

> Create Common Works Registration 2.1 files, check and read existing .V21 files, and understand society ACK responses in one free browser tool.

*Published by [TrackForge](https://trackforge.studio) · Last updated 2026-11-18*

- **Tool:** https://trackforge.studio/cwr-tool/workbench
- **Supported standard:** Common Works Registration 2.1 Revision 8
- **Supported public file type:** .V21

---

The TrackForge Common Works Registration (CWR) validator and generator helps publishers and rights administrators create a CWR 2.1 file, check or read an existing .V21 file, and understand a society acknowledgement response (ACK).

## Choose a task

### Create a registration file

Build a Common Works Registration 2.1 file from a form or CSV, then download it for review and submission.

**Before you begin:** You will need your sender identity, works, writers, publishers and rights shares.

[Open Create](/cwr-tool/workbench?tab=generate)

### Check an existing file

Choose a CWR 2.1 source file, check it for structural, field, share and destination-rule problems, then open supported files in the editor to amend them.

**Before you begin:** You will need the source registration file you plan to submit or re-submit; society responses belong in Society response.

[Open Check](/cwr-tool/workbench?tab=validate)

### Read an existing file

Turn a registration file into a readable view of its works, writers, publishers and rights shares.

**Before you begin:** You will need the registration file you want to understand.

[Open Read](/cwr-tool/workbench?tab=inspect)

### Understand a society response

Upload a society acknowledgement response (ACK) to see what was accepted, rejected or needs attention.

**Before you begin:** You will need the acknowledgement file returned by the society.

[Open Society response](/cwr-tool/workbench?tab=parse-ack)

## Available features

- Create Common Works Registration 2.1 .V21 files from a form or CSV.
- Check existing CWR 2.1 and 2.2 files (.V21 and .V22) for structural, field, share and available destination-profile problems.
- Read works, writers, publishers and rights shares from an existing .V21 or .V22 file.
- Understand society acknowledgement responses (ACKs) by accepted, rejected and attention-needed outcome.
- Open supported .V21 files in the editor, correct identified issues and download a regenerated file without changing the original upload.
- Use plain-language issue explanations with technical evidence kept available under Technical details.
- Use all four public tasks without creating an account.
- Convert a completed LyricFind spreadsheet into LyricFind’s lyric-1.2 lyrics file or its preferred ownership-1.4 file with ownership and lyrics together, with a review list of rows to fix and values to confirm; uploads are converted and then discarded, never stored.
- Keep each work’s lyrics in the CSV template’s optional Lyrics column or on the work itself, and make LyricFind’s lyric-1.2 file from the works you are building; lyrics are never put in the CWR file and are converted and then discarded, never stored.
- Give a recording’s release barcode in the CSV template’s Release EAN/UPC column or in the work card; a 13-digit EAN is written into the file as it is, and a 12-digit UPC with a leading 0, which is how the file holds it.

## Destination submission requirements

These recipient policies sit outside the CWR file-format checks and must be confirmed before submission.

### CAPASSO for Africa

CAPASSO collects mechanical rights only. Any company can collect the performing share, but the mechanical share must be collected by a direct CAPASSO member, and any sub-publisher or administrator on the work must be a direct CAPASSO member too. TrackForge names each publisher whose mechanical society is not CAPASSO, so you can confirm it is a member before you send the file.

### CAPASSO for English- and Portuguese-speaking regions

CAPASSO collects mechanical rights only. Any company can collect the performing share, but the mechanical share must be collected by a direct CAPASSO member, and any sub-publisher or administrator on the work must be a direct CAPASSO member too. TrackForge names each publisher whose mechanical society is not CAPASSO, so you can confirm it is a member before you send the file.

## Roadmap

The roadmap uses only three states and does not promise a date without an owned delivery commitment.

### Available now

Implemented in the free CWR tool and backed by a dated release entry.

- **Create, check, read and understand responses** — Four outcome-led public tasks cover CWR 2.1 generation, .V21 checking and reading, and society acknowledgement-response review.
- **Correct a file in your Workspace** — Check a file here, then select Edit in my Workspace: the file is carried across, its works open for correcting, and the original upload is never changed.
- **Society-led CWR generation choices** — Choose familiar destinations including The MLC, PRS for Music / MCPS via ICE, CMRRA, CAPASSO for Africa, CAPASSO for English- and Portuguese-speaking regions, ABRAMUS, AllTrack Worldwide, AllTrack US-only, SACEM, SIAE and SGAE. TrackForge states whether it applies recipient-specific checks or the common CISAC Base CWR 2.1 rules.
- **LyricFind lyrics files** — Turn a completed LyricFind spreadsheet into the lyric-1.2 lyrics file or LyricFind’s preferred ownership-1.4 file with ownership and lyrics together, with a review list of rows to fix and values to confirm. Uploads are converted and then discarded, never stored.

### In development

Actively being implemented, without an unowned delivery date.

Nothing is publicly committed to active development right now.

### Exploring

A direction under consideration, not a delivery promise.

- **Additional recipient-specific checking** — Further destination rules will move forward as current technical guidance and recipient evidence are verified. A GEMA file needs CWR 2.2 with GEMA’s own records for the music and lyrics split, which TrackForge does not write.
- **Public integration access** — A governed way to integrate the tool’s capabilities with other systems is being considered. No public API, webhook contract or delivery date is promised.

## Common questions

**What is a CWR file?**

Common Works Registration (CWR) is the CISAC file format publishers use to tell collecting societies who wrote and publishes a musical work, how rights are shared, and what should be registered.

**What can I do in the CWR validator and generator?**

The free CWR tool has four tasks: create a CWR 2.1 .V21 file, check an existing .V21 file, read a file in plain language, and understand a society acknowledgement response (ACK).

**How is the free tool different from the Workspace?**

The free tool checks a file, reads a society reply and makes a file by hand, with no account. The Workspace holds your whole catalogue, checks every work against what the societies hold, sends your registrations and reads the replies for you. It is free during the beta.

**Which CWR version and destination profiles does the free CWR tool support?**

The free CWR tool creates Common Works Registration 2.1 Revision 8 .V21 files. Society choices include The MLC, CMRRA, AllTrack Worldwide, AllTrack US-only, CAPASSO for Africa, CAPASSO for English- and Portuguese-speaking regions, ABRAMUS, PRS for Music / MCPS via ICE, SACEM, SIAE and SGAE; the interface states whether recipient-specific rules or CISAC Base checks are being applied. Every one of them accepts CWR 2.1, so there is no version to choose and no CWR 2.2 option. It checks and reads both CWR 2.1 and CWR 2.2 files, each against the version the file declares, and the Workspace loads the works from CWR 2.1 and 2.2 files made by other systems. The tool does not make a file for GEMA, which asks for CWR 2.2 with its own extra records: register GEMA works through GEMA’s online portal or the CWR route you already use for GEMA.

**What does receiver 000 mean?**

Receiver 000 means multiple or unspecified recipients. It remains a valid CWR receiver code, but CISAC Base checks alone do not assess a known recipient’s own profile or prove that one file is ready for every society.

**Can I keep lyrics in the same spreadsheet as my works?**

Yes. Tick “Include a Lyrics column” when you download the CSV template, and put each work’s lyrics in that column. CWR has no place for lyric text, so lyrics are never put in the CWR file. When any work has lyrics, the LyricFind lyrics file panel below Generate makes LyricFind’s lyric-1.2 file from them, using each work’s Work ID as its SongID.

**Does passing validation guarantee society acceptance?**

No. A passing result means the named CWR structure and selected destination-profile checks found no blocking issue. A society can apply additional policy or data checks, and only its acknowledgement response confirms the outcome of a submission.

## Scope and limitations

- The free CWR tool does not submit files to a collecting society or promise that a recipient will accept them.
- The free CWR tool creates Common Works Registration 2.1 Revision 8 files (.V21) and nothing else: every society it offers accepts CWR 2.1, and there is no CWR 2.2 option. It checks and reads CWR 2.1 and CWR 2.2 files (.V21 and .V22), each against the version the file declares. Its editor opens CWR 2.1 files only. The Workspace loads the works from CWR 2.1 and 2.2 files made by other systems and keeps the original file unchanged.
- CWR 2.1 generation is available for CISAC Base, The MLC, CMRRA, AllTrack Worldwide, AllTrack US-only, CAPASSO for Africa, CAPASSO for English- and Portuguese-speaking regions, ABRAMUS, PRS for Music / MCPS via ICE, SACEM, SIAE and SGAE. A separate PRS-specific checking profile remains available for uploaded files.
- The MLC, SACEM, SIAE and SGAE choices currently use CISAC Base CWR 2.1 checks; TrackForge does not yet assess every requirement specific to those organisations.
- The free CWR tool does not make a file for GEMA. GEMA asks for CWR 2.2 with its own extra records for the music and lyrics split, which TrackForge does not write. Register GEMA works through GEMA’s online portal or the CWR route you already use for GEMA.
- Receiver 000 means multiple or unspecified recipients. Under CISAC Base it does not claim that any named society’s destination-specific requirements were assessed.
- Additional society profiles and public integration access remain exploratory until implementation and evidence exist.
- The LyricFind lyrics file is not sent to LyricFind: you add your LyricFind login and upload it yourself.
- Saving your progress does not keep lyrics: keep them in your spreadsheet’s Lyrics column, or use Save to workspace, where they are kept with each work.

## Help and updates

- [Help and plain-language issue explanations](https://trackforge.studio/docs/cwr/problems-and-fixes)
- [Dated updates](https://trackforge.studio/cwr-tool/updates)
- [Roadmap](https://trackforge.studio/cwr-tool/updates#roadmap)

---

Source: [https://trackforge.studio/cwr-tool](https://trackforge.studio/cwr-tool)
