Most people keep their songs in whatever was nearest: a notes app, a screenshot of somebody else's tab, a document where the chords are held above the right syllable by a row of spaces and a prayer. It works until the day the font changes, or the phone does, and every chord slides half a line to the left.
ChordPro is the fix, and it is older than most of the apps that read it. It is a plain-text format — no proprietary file, no account, no export button — in which a chord is written in square brackets, inline, at the exact point in the word where you change your hand.
What it looks like
{title: The Last Bus Home}
{artist: Nina Kovač}
{key: Am}
{capo: 2}
[Am]The last bus home is [F]late
and I am [C]singing any[G]way
That is the whole idea. The brackets sit inside the line, glued to the syllable they belong
to, so nothing can drift: Am is on "The", F is on "late", and
they stay there whether the line is rendered at twelve points on a phone or forty on a tablet
propped against a music stand.
The lines in curly braces are directives — metadata about the song rather than the song itself. You will meet a handful of them constantly:
{title: …}and{artist: …}— what the song is called and whose it is.{key: …}— the key it is written in, which is what lets an app name the key you land in when you transpose, instead of guessing it from the chords.{capo: …}— where the capo goes, if it goes anywhere. Separate from the key on purpose: those are two different facts and a sheet that conflates them makes both of them useless.{comment: …}— a note to yourself, printed alongside the words.
Anything an app does not understand, it is expected to ignore rather than choke on. That is deliberate, and it is most of why the format has lasted: a file written for one program in 2011 still opens in a program written last year, minus whatever the newer one never learned.
Where exactly the bracket goes
The one thing worth getting right on your first file is that a chord marks the syllable where your hand moves, not the word it is nearest to. Look again at the second line above:
and I am [C]singing any[G]way
The G is inside "anyway", between "any" and "way", because that is where the
chord actually changes when you play it. Written as [G]anyway it would come two syllables
early; written at the end of the line it would be too late to be any use. A chord that lands
mid-word is not a mistake in the file, it is the file being precise.
This is also the part that makes the format tedious to type by hand and worth converting into rather than retyping. If you already have sheets with the chords sitting above the words, a free converter reads the columns and writes the brackets, and you check the result rather than doing the work.
Why the brackets beat the spaces
The "chords above the words" layout everybody starts with is not really a format — it is a picture of one. It depends on the text being monospaced, on nobody wrapping a long line, and on every future reader having the same column width you did. Change any of the three and the information is gone, because the information was the alignment.
ChordPro stores the relationship instead of a picture of it. Once a chord is attached to a syllable rather than to a column, an app can do things that are impossible in a screenshot:
- Transpose. Every chord moves by the same interval, and the words do not move at all — which is what a transposer is doing when it hands you back the same sheet in a different key.
- Apply a capo and show the shapes your hand actually plays, not the ones the recording is in.
- Reflow on a narrow screen without the chords ending up over the wrong word.
- Switch notation, so an Italian musician reads
Lawhere an English one readsA— the same file, two readers.
None of that is clever. It is all downstream of one decision: write down which syllable, not which column.
Marking up the parts of a song
Once the chords are in, the second useful thing a ChordPro file can carry is structure. A chorus is wrapped in a pair of directives, and so is a block of tablature:
{start_of_chorus}
[F]Sing it again, and [C]again
{end_of_chorus}
{start_of_tab}
e|---0---2---3---|
B|---1---3---0---|
{end_of_tab}
Both pairs have short forms — {soc} and {eoc}, {sot} and {eot} — and both mean the
same thing to a reader as to a program: this block is different from the verse around it. The
tab pair matters more than it looks. A tab block tells the app to leave the rows alone:
not to reflow them, not to read the letters at the start of each line as chords, not to touch
the alignment that is the entire content of a tablature row.
What ChordPro does not do
It is a lyric-and-chord format, and being honest about the edges is the fastest way to know whether it fits your repertoire:
- Rhythm is an add-on, not the core. A lyric line gives you the order and the placement,
not the duration: nothing in it says that the
Flasts two bars and theClasts one. The format has a chord-grid block for bar-by-bar charts, but most files never use it. - It does not carry a melody itself. A file may embed ABC or LilyPond notation for another program to engrave, but if notes on a stave are the point, you want notation software.
- It does not carry audio. Backing tracks, click tracks and recordings live outside it, and apps that support them do it with their own extensions.
- Apps disagree about the rarer directives.
{a: …}is the artist in one program and the album in another;{st: …}is a subtitle in the specification and was redefined by a popular app to mean the artist. The core — brackets,{title},{key}, choruses — is universal; the edges are dialect. Anything importing a large library should be sniffing which program wrote a file before trusting its metadata.
Where it came from
The format is older than almost everything that reads it, and the story is unusually small.
In June 1991 two developers, Martin Leclerc and Mario Dorion, turned up early for a tennis
game and had half an hour to fill. What they sketched was a notation for writing chords into
a line of lyrics, and the program to typeset it: Chord, released from 1992, which took a
text file of songs and printed a clean lead sheet. The bracket convention this whole article
is about was invented at a tennis court, waiting.
The program spread, and the files spread further. Nobody planned the name — people started
calling them "ChordPro" files, and by the time anyone noticed, that was what they were called.
The last release of the original Chord was version 3.6.2, in July 1995.
That should have been the end of it. Instead a user named Johan Vromans, who had picked the
tool up in 1992 and quietly kept improving it for himself, was persuaded in 2007 by another
user, Adam Monsen, that the work should not be lost. He published his version — first as
Chordie, renamed Chordii to stop it being confused with a website — and maintained it
for another decade. In 2016 he started again from nothing, in Perl, and the result is the
program now called ChordPro, named after the format rather than the other way round. Its
first alpha was released on 4 June 2016.
The language itself is on version 6; version 5 was drafted and never shipped, folded into 6 before release, and version 6 is what a current file is written against. The specification lives at chordpro.org — the cheat sheet is a single page and covers everyday use — and the reference implementation is on GitHub, open source, still maintained, and decides the rest.
There is no standards body, no committee and no company, which cuts both ways. It is why the rarer directives drift between apps, and it is also why the format has cost nobody a licence fee, an account or a migration in thirty-five years. The core has not changed since the tennis court: a chord in square brackets, glued to its syllable.
It outlives the app
The quiet argument for ChordPro is not any feature. It is that the file is readable by a
human being with a text editor, twenty years from now, on a device nobody has designed yet.
That is not a hope, which is the point of the history above: a file written for Chord in
1993 still opens today, and the program that wrote it has been gone since 1995. A repertoire
is a thing you build slowly and expect to keep; storing it in a format only one company can
open is how people lose a decade of work when that company is bought.
The files themselves are ordinary text with an unglamorous set of extensions — .chopro,
.cho, .crd, .pro — and any of them opens in any editor on any machine. That is not a
low bar cleared by accident. It is the bar.
If your songs are already in the spaces-and-prayer layout, they are not lost — the conversion is mechanical, and a decent importer will do it for you and show you the result before it saves anything, because the conversion is a heuristic and it will not always guess right. The longer piece on converting covers where it goes wrong and how to spot it.
What matters is where they end up: in a format that will still be a format when the app has changed hands, or names, or gone.
Questions people ask
- Who invented ChordPro, and when?
- Martin Leclerc and Mario Dorion, who sketched the notation in June 1991 and released the Chord program that read it from 1992. The name came from users rather than from the authors: the files simply became known as ChordPro files. Johan Vromans maintained the tool from 2007 and rewrote it from scratch in 2016 as the program now called ChordPro, which is the reference implementation of the format today. The current language version is ChordPro 6, specified at chordpro.org.
- What is a ChordPro file?
- A plain-text file holding lyrics with the chords written inline, in square brackets, at the syllable where the chord changes. Lines in curly braces carry metadata such as the title, the key and the capo position. It is ordinary text, so it opens in any editor on any device, and it usually has the extension .chopro, .cho, .crd or .pro.
- How do I open a .chopro file?
- Any text editor will show you the contents, because the file is plain text — there is nothing proprietary to decode. To read it as a formatted song sheet, with the chords sitting above the words and the option to transpose, you need an app that understands the format. Most chord chart apps for musicians do, which is the point of using it.
- Is ChordPro the same as guitar tab?
- No. Tab describes which string and fret to play, note by note, and ChordPro describes which chord to hold and when to change it. They answer different questions and often appear together: ChordPro can carry a block of tablature verbatim between start_of_tab and end_of_tab directives, which tells an app to leave those rows exactly as they are.
- Can I convert my existing chord sheets to ChordPro?
- Yes, and it is usually one paste. A sheet with the chord names on a line above the words can be read column by column and rewritten with the chords in brackets, because the column each chord sits in is what says which syllable it belongs to. The conversion is a heuristic rather than a certainty, so read the result before you keep it.
