---
title: "CWR 2.1 vs 2.2: which version should you send?"
description: "What CWR 2.1 and CWR 2.2 are, what 2.2 adds, which societies take which version, and why 2.1 is still the right default for most publishers."
image: "https://trackforge.studio/docs/img/trackforge-social-card.png"
---

> Documentation Index
> Fetch the complete documentation index at: https://trackforge.studio/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# CWR 2.1 vs 2.2: which version should you send?

> Send CWR 2.1 unless the recipient requires 2.2, or you need several society work numbers on one work. That is the whole answer for most publishers. The rest of this page explains why.

*Published by [TrackForge](https://trackforge.studio), 16 November 2026. Society positions last checked on 18 November 2026.*

---

## The short answer

I get asked this more than almost anything else about CWR: 2.2 is newer, so shouldn't everyone be on it? No. 2.2 is not a better 2.1 that you upgrade to. It is the same format with a few extra fields, and those fields only help if the society receiving your file reads them.

2.1 is accepted almost everywhere. A 2.2 file sent to a society that only reads 2.1 is usually refused before anyone looks at a work. So the question is not which version is better. It is which version your recipient takes, and whether you have data that only 2.2 can carry.

There are two good reasons to send 2.2 today:

1. **The recipient requires it.** GEMA does now for direct CWR. APRA AMCOS may from late 2027 (see below).
2. **You need several work numbers on one work.** If you hold a work's numbers at several societies and want to deliver them in one registration, 2.2's XRF record is the only way to do it in the file.

If neither applies, 2.1 is the right choice. A clean 2.1 file that registers is worth more than a 2.2 file that is refused or half-read.

## What each version is

Both versions are CISAC standards. Both are fixed-width text: each record type has a set length and every field sits at a set position. Neither version uses variable-length records.

- **CWR 2.1** is the long-standing standard. The current text is Revision 8 (CISAC CWR11-1991R4, adopted 5 November 2019). Revision 8 changed only the file header, so that sender IPI numbers longer than nine digits fit. Revision 7 (November 2013) is still what some societies quote.
- **CWR 2.2** was approved by CISAC's Information Services Committee in Lisbon on 14 April 2016. The current text is Revision 2 (CISAC CWR19-1070R1). CISAC describes it as containing minor changes from 2.1 Revision 7.

The file name tells you which version a file is: `.V21` or `.V22`.

## What 2.2 adds

| Area | What changes in 2.2 | Who it helps |
|---|---|---|
| **XRF** (new record) | Carries another organisation's identifier for the work, such as a society work number. One XRF per identifier, so one work can carry several. | Publishers that hold the same work's numbers at several societies |
| **REC** (recording detail) | New fields: recording title, version title (for example "remixed by"), display artist, record label, an ISRC validity flag and your own recording ID | Matching usage to the right work when titles differ between work and recording |
| **PWR** (publisher for writer) | A **publisher sequence number** is now mandatory. It says which publisher chain each writer link belongs to. A missing or wrong one rejects the transaction. | Works with more than one original publisher, where 2.1 could leave the link ambiguous |
| **SPU** (controlled publisher) | Your own publisher records must carry their IPI Name Number | Recipients matching you as the submitter |
| **HDR** (file header) | Version, revision, software package and software version | Recipients tracing which system produced a file |
| **OPT / OWT** (new, optional) | Collection shares for publishers and writers you do not control | Showing total collection where shares change on sub-publication. CISAC says these are not authoritative. |
| **ORN** (work origin) | ISAN and EIDR identifiers for audiovisual productions | Production music and screen work |

ICE's own CWR overview names the same two practical gains. 2.2 lets you define claims more precisely, through the publisher sequence number, and its XRF records are an easier way to deliver several society work numbers.

## Who takes which version

Each row names its source. Where a society has not published its position, I say so.

| Recipient | Versions accepted | Basis |
|---|---|---|
| **ICE** (PRS for Music, MCPS and the other ICE societies) | 2.1 and 2.2 | Published: ICE's CUBE Agreement and CWR Overview |
| **The MLC** (US mechanicals) | 2.1 (all revisions) and 2.2. 3.1 is listed as pending. | Published: The MLC CWR User Guide, May 2024 |
| **GEMA** | 2.2 only, for direct CWR | Published: GEMA's page on registering works by CWR |
| **APRA AMCOS** | 2.1 Revision 7 only, today | Reported by a member, from the APRA AMCOS CWR FAQ. Not found on APRA AMCOS's public site. |
| Other societies | Check with the recipient | 2.1 remains the common ground |

**GEMA is moving to ICE.** GEMA's own statements differ on the route in the changeover. Its letter to CWR publishers says they report directly to ICE from 2 November 2026, and that those files are processed from January 2027. Its ICE GetOn timeline, as read on 18 November 2026, says publishers who report by CWR keep sending to GEMA as usual, and ICE processes the files from 10 December 2026. Both give go-live in mid-December 2026 and the first distribution on ICE data on 1 April 2027. Ask GEMA (icegeton@gema.de) where to send a file before you plan around either. GEMA has not said which CWR version a file for its repertoire must be in once it goes to ICE, and it says ICE will process GEMA's records for the music and lyrics split. So I would not assume a 2.1 file to ICE is enough for GEMA's repertoire.

**APRA AMCOS may switch in late 2027.** A member tells us APRA AMCOS will stop taking 2.1 in November 2027, and that it has not yet chosen between 2.2 and 3.0 to replace it. I treat that as a signal to watch, not a fact. APRA AMCOS has not published it.

## The cost of getting it wrong

Recipients read the version from the file: the version field in the header and the version number in the group header. A society that only reads 2.1 will usually refuse a 2.2 file outright. The cost is not a field or two lost but the whole delivery, and you only find out when the acknowledgement comes back.

The reverse risk is smaller but real. A 2.2 file sent to a society that accepts 2.2 but ignores fields it does not use will register, but the extra work you put into XRF or recording data does nothing there.

## What about CWR 3.x?

CISAC has drafted a 3.x generation. It is not in general use. The MLC lists 3.1 as pending and asks interested submitters to contact it first. I would not build for 3.x until the societies you send to ask for it. If APRA AMCOS chooses 3.0 for 2027, that will be the first real pressure to.

## What TrackForge does

The position on 18 November 2026:

- **Every file you create is CWR 2.1 Revision 8 (`.V21`).** That holds in the free CWR tool and in the Workspace, for every society either one offers, because each of those societies accepts 2.1. You do not choose a version and there is no CWR 2.2 option. In the Workspace the prepared file's page shows the version.
- **TrackForge's engine also writes CWR 2.2 Revision 2, and no product screen offers it.** Every society we prepare for accepts 2.1, so a 2.1 file is the file to send to each of them.
- **Checking.** The checker works to the version a file declares, 2.1 or 2.2. The free CWR tool's check and reader take `.V21` and `.V22` files, and the [MCP tool](https://trackforge.studio/mcp) `validate_cwr` takes the text of either version. For 2.2 it checks the header, recording, publisher-for-writer and cross-reference rules, not the optional OPT, OWT and ORN records.
- **Opening and importing.** The free tool's editor, Workspace import and Workspace registration history read CWR 2.1 files only. Society replies are read in the acknowledgement layout that 2.1 and 2.2 share; a reply that states version 2.2 is not read.
- **GEMA.** TrackForge 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.

If you are deciding now, my advice is simple. Send 2.1 to everyone who takes it. Send 2.2 only where the recipient requires it, or where several society work numbers on one work justify it. Check again in 2027 if you register in Australia or New Zealand.

## Sources

- CISAC, *Functional specifications: Common Works Registration Version 2.2, Revision 2* (CWR19-1070R1): revision history, HDR, REC, PWR and XRF records.
- CISAC, *Functional specifications: Common Works Registration Version 2.1, Revision 8* (CWR11-1991R4).
- ICE / PRS for Music, *CUBE Agreement and CWR Overview*: "ICE supports the use of both CWR 2.1 and CWR 2.2".
- The MLC, *CWR User Guide*, May 2024: accepted versions.
- GEMA, [Work declarations in the CWR format](https://www.gema.de/en/music-creators/repertoire/registration/work-declarations-in-the-cwr-format), and GEMA's [ICE GetOn timeline and questions](https://www.gema.de/en/about-gema/organisation/ice-international-copyright-enterprise/advanced-information), read 18 November 2026.
- APRA AMCOS CWR FAQ, as supplied by a member (October 2026). Not published on the APRA AMCOS site.

## Related

- **[What CWR is](/docs/cwr)**: the format, the workflow and the society landscape.
- **[CWR record types](/docs/cwr/record-types)**: every record in a CWR file.
- **[What each society requires](/docs/cwr/society-requirements)**: recipient rules that sit outside the file format.
- **[CWR validator and generator](https://trackforge.studio/cwr-tool/workbench)**: create or check a CWR 2.1 file. Free, no account required.

Source: https://trackforge.studio/docs/cwr/cwr-2-1-vs-2-2/index.mdx
