The short answer
ChordPro is a plain text format for writing songs with chords. You type the words, and you put each chord in square brackets right before the syllable where it changes:
[G]Amazing [C]grace, how [G]sweet the sound
Everything else about a song, such as its title or key, goes in curly brackets on its own line:
{title: Amazing Grace}
{key: G}
That is most of the format. Because it is only text, the chords stay attached to the right syllable at any font size or screen width, which is the problem with the old way of lining chords up over words using spaces. An app can also transpose it, because it knows exactly which characters are chords.
The one rule that matters
Put the chord immediately before the letter it is played on, with no space.
[G]Ama[C]zing grace
Here the G lands on the "A" of Amazing, and the C lands on "zing". If you read the line aloud, the chord change falls on the syllable right after the bracket.
Common mistakes:
- A space after the bracket.
[G] Amazingputs the chord on a gap. - Round brackets.
(G)Amazingis just text. - Lowercase chord names. Write
[Am], not[am].
Chords can be as detailed as you need: [Gmaj7], [D/F#], [Bb], [Csus4].
For a line with no words, such as an intro or turnaround, write the chords on their own line:
[G] [C] [D] [G]
The directives you will actually use
Directives are the curly-bracket lines. The full ChordPro specification has many, but a worship song needs only a handful.
About the song:
{title: Amazing Grace}{artist: John Newton}{key: G}{tempo: 72}{time: 3/4}{capo: 2}
Marking the sections:
{start_of_verse: Verse 1}
[G]Amazing [C]grace, how [G]sweet the sound
{end_of_verse}
{start_of_chorus: Chorus}
[C]A chorus line goes [G]here
{end_of_chorus}
There are short forms too, {soc} and {eoc} for the chorus, {sov} and {eov} for a verse, and {sob} and {eob} for a bridge. {start_of_bridge} works in full as well.
Parts without their own directive, such as a pre-chorus, a tag or an ending, are usually marked with a comment:
{comment: Pre-Chorus}
A line beginning with the hash character is a note to yourself, and apps ignore it.
A whole song, start to finish
{title: Example Song}
{artist: Your Name}
{key: G}
{tempo: 76}
{time: 4/4}
{comment: Intro}
[G] [C] [D] [G]
{start_of_verse: Verse 1}
[G]This is how a [C]verse looks
[Em]Chords sit [D]right before the [G]word
{end_of_verse}
{start_of_chorus: Chorus}
[C]This is how a [G]chorus looks
[C]Short, and [D]easy to [G]find
{end_of_chorus}
Save it as a text file ending in .cho. That is a complete, working song.
Writing tips
Type the words first. Get the lyric right, then add chords in a second pass while listening or playing. It is much faster than doing both at once.
Keep lines the length you want them on the page. Line breaks are yours to choose, so break where a singer would breathe.
Write the key you really play in, or note it. If the original chart is in A and your band plays in G, decide which one the file holds. An app can transpose from the written key, but it has to be told the truth about what that key is.
Name sections consistently. "Verse 1" and "Chorus" are understood by most apps. Creative names may not be.
Moving songs in and out of Broadcasteer
Broadcasteer reads and writes ChordPro from the song editor. Open New Song or Edit Song, and beside the Key field you will find the buttons.
Import ChordPro takes .cho, .chordpro, .chopro, .crd, .pro and .txt files. A .txt can be proper ChordPro, or a plain sheet with chords typed over the words, which is converted so each chord lands on the letter below it. That conversion depends on the spacing in your file, so read it through afterwards.
On import it keeps the title, artist, key, tempo, time, capo and section names. A few things it deliberately does not bring in:
- Tab, grid, ABC, LilyPond, SVG and text blocks are skipped.
- A bare
{chorus}directive, the kind that means "repeat the chorus here", does not repeat anything. Use your song order for that. {define}and{new_page}keep nothing.- If a chart has more than one tempo or time, the first is kept and a note tells you.
If no key is given, Broadcasteer guesses one from the chords. Check it.
Export .cho saves the song as a ChordPro file for other band apps. Both a tempo word and a tempo number are written, each on its own {tempo} line, words first, so reading the file back restores both.
Export .txt beside it saves only the words under their section titles, with no chords. This is useful for a printed lyric sheet or for handing words to someone else.
Hold marks
Charts sometimes stretch a word across a chord change, written with a dash:
hallelu - [D]jah
Broadcasteer keeps that mark in the chart and the Chords view, for the band. On the projector, the stream and every words-only screen, it reads simply "hallelujah", so the congregation never sees a broken word.
What ChordPro is not
It is not sheet music. It has no notes, rhythms or melody, only words, chords and structure. If your band reads a score, this will not replace it.
It is also not one fixed thing across apps. Most apps agree on the brackets and the common directives, and disagree at the edges. Keep to what is on this page, and your songs will travel well.

