ChordPro support
ChordPro is a plain-text based standard that can be edited in any text editor on any platform. Lyrics are written as normal text, chords are inline with the lyrics, surrounded by square brackets([ and ]), and meta data is specified using “tags” surrounded by { and } characters.
As a simple example, a song file might look like this:
{title: Amazing Grace}
{artist: John Newton}
{key: D}
{start_of_verse: Verse 1}
A[D]mazing grace! (how [G]sweet the [D]sound)
That [D]saved a wretch like [A7]me!
I [D]once was lost, but [G]now am [D]found,
Was [D]blind, but [A7]now I [D]see.
When displayed, the above file may appear like this:

The format is used by many lyric and chord apps. Unfortunately, while the central elements of the format are usually treated the same across many apps, there can be quite substantial differences in how some of the tags are interpreted and used, especially with older programs. And of course, each app can have its own custom tags that none of the other apps understand.
SongSheet Pro does its best to support the currently published ChordPro standard as documented at https://www.chordpro.org/chordpro/index.html.
You can export your songs to this format, and import them too.
SongSheet Pro imports a number of non-standard tags so that it can read files from apps that don’t follow the ChordPro standard. They are listed in the import reference below, and tags it doesn’t recognize are skipped. If a ChordPro file doesn’t import the way you expect, send a support request with a sample file.
SongSheet Pro also supports exporting to a reduced set of ChordPro tags that most other programs should be able to support. This is documented in the ChordPro v4.6 specification.
Importing ChordPro
The table below lists the tags SongSheet Pro reads when importing a ChordPro file.
SongSheet Pro matches tag names exactly. Capital letters don’t matter, but spelling does: a misspelled tag such as
{meta: note …}(instead of{meta: notes …}) or{start-of-verse}(instead of{start_of_verse}) is skipped without any message, and its line does not appear in the song. If part of a file is missing after you import it, check the spelling of its tags. Put each tag on its own line. A tag with no closing}is treated as lyrics, so it appears in the song.
| Imported value | Preferred tag | Also accepted | Notes |
|---|---|---|---|
| Title | title |
t |
If there is none, the file name is used. |
| Artist | artist |
author, subtitle, st, su |
subtitle, st and su are read only if there is no artist or author tag. |
| Composer | composer |
||
| Lyricist | lyricist |
||
| Arranger | arranger |
||
| Copyright | copyright |
||
| Year | year |
||
| Key | key |
k |
|
| Capo | capo |
ca |
|
| Tempo | tempo |
bpm, metronome |
Beats per minute, as a whole number. |
| Time signature | time |
||
| Duration | duration |
Controls how fast the song auto-scrolls. Seconds (210) or minutes and seconds (3:30). |
|
| Tags | genre |
A single genre tag is split by commas and semicolons into several tags. |
|
| CCLI song number | ccli |
||
| Song notes | notes |
keywords |
Repeated notes tags become separate lines. keywords is used only if the file has no notes tag, and if there are several, the last one is used. |
| Chord palette | chords |
Adds chords to the song’s chord palette. Chords are separated by spaces, and _ is used for spaces within chords. |
|
| Comment | comment |
c, comment_italic, ci, comment_box, cb |
A comment on the first line of an unnamed section becomes the section’s name. |
| Verse | start_of_verse and end_of_verse |
start_of_part and end_of_part, sop and eop, name |
Creates a stanza with the given name. start_of_verse with no name defaults to “Verse” in the app’s language. The other tags leave the section unnamed. |
| Chorus | start_of_chorus and end_of_chorus |
soc and eoc |
The name defaults to “Chorus”, in the app’s language. |
| Tab | start_of_tab and end_of_tab |
sot and eot |
Creates a tablature. A comment directly before it, with nothing else in the section, becomes its name and wins over any text after the tag. Otherwise the name is the text after the tag, if any. A tab has no default name. |
| Chorus reminder | chorus |
Adds an unnamed section containing one line that says “Chorus”, in the app’s language. |
How tags are read
- Any tag in the table can also be written as
{meta: name value}, so{meta: key G}and{key: G}are imported the same way. Other apps may accept this form only for song information such as the title or key. - Some of these tags are not part of the ChordPro standard, for example
ca,name,genre,ccli,start_of_partandsop. SongSheet Pro accepts them so that files from other apps, and its own exports, import completely. - If a file has several
artist,composer,lyricistorarrangertags, they are all imported and separated by;. Fortitleandcapo, the last tag is used. Forkeyandduration, the first tag is used. Fortimeandtempo, the first valid tag is used.
Sections
- The end tag of a verse, chorus or tab section is optional, because a blank line also ends the section.
start_of_partandsoptreat the lowercase textchords_like,repeatandguitar_onlyspecially: the text before the first one is the section name, and that word and everything after it become a comment at the top of the section. Every other section tag uses the whole text as the name.- SongSheet Pro has no separate chorus section type. A chorus is a verse-type section whose default name is “Chorus” (in the app’s language), so
{start_of_chorus}and{start_of_verse: Chorus}import as the same kind of section.
Setlist files
A setlist exported to ChordPro cannot be imported back as a setlist: it comes in as one song containing each of the setlist’s songs once, joined together and named after the last song. The summary at the top of the file becomes lyrics, the {new_song} tags between the songs are ignored, and the sets are not restored. To move a setlist between SongSheet Pro users, use the SongSheet format.
Unsupported tags
SongSheet Pro doesn’t support all the features of ChordPro, especially around formatting directives. SongSheet Pro has its own typesetting and theme system, so it doesn’t support any of the tags around defining fonts, colors, page breaks, column breaks, or images.
Also, since SongSheet Pro doesn’t (yet) support chord diagrams, it doesn’t support chord grids or the tags that define chord diagrams/fingering.
Finally, all the various “comment” directive variations are treated as a single comment type.
SongSheet Pro has no album field, so an {album: …} tag is ignored. Lines that start with # are ChordPro comments and are skipped. Any other tag that is not in the table above is also skipped without any message, and its line does not appear in the song.
Exporting to ChordPro from SongSheet Pro
SongSheet Pro can produce ChordPro-formatted content for use in other apps. Every tag it writes when exporting a song can be read again when importing it, but only the tags listed below are written, so ChordPro export is lossy. Don’t use it to send songs to other SongSheet Pro users, or to back up or archive your songs: use the SongSheet format instead. A setlist exported to ChordPro can’t be imported back as a setlist either (see Setlist files).
Export song to ChordPro
- From the song view, open the Share Sheet and select Export As.
- Choose your format, either ChordPro v4.6 (older apps may not recognize the newer tag formats) or ChordPro v5.0.
- Send the song via AirDrop, choose an app to open the ChordPro file in, copy to clipboard, or save it to Files.
ChordPro is not offered for a song imported from a PDF, RTF or Word file.
ChordPro v5.0 export
This is the fullest version of the format SongSheet Pro exports. A tag is written only when the song has that value.
| Song content | Tag written |
|---|---|
| Title | {title: Amazing Grace} |
| Artist | {artist: John Newton} |
| Composer | {composer: Mozart} |
| Lyricist | {lyricist: Charles Wesley} |
| Arranger | {arranger: Jane Smith} |
| Copyright | {copyright: © 2020 Example Music} |
| Year | {year: 1999} |
| Key | {key: C} |
| Capo | {meta: capo 3} |
| Tempo | {tempo: 135} |
| Time signature | {time: 4/4} |
| Duration | {duration: 210} |
| Tags | {meta: genre Blues, Slow} |
| CCLI song number | {meta: ccli 123456} |
| Song notes | {meta: notes Play softly}, one tag per line of notes |
| Comment | {c: Play softly} |
| Verse | {start_of_verse: Verse 1} and {end_of_verse} |
| Chorus | {start_of_chorus: Chorus} and {end_of_chorus} |
| Tab | {start_of_tab: Riff} and {end_of_tab} |
A name is written only when the section has one. A section whose name starts with “Chorus”, such as “Chorus 2”, is written as a chorus, and its name is kept. Chorus names are recognized in English only, ignoring capital letters, so a section named “Refrão” is written as a verse named “Refrão”.
ChordPro v5.0 files are saved as UTF-8.
ChordPro v4.6 export
This is the compatibility version, with fewer tags so that older apps can read it. SongSheet Pro writes only the tags in the table below. Other tags, such as key and capo, are not written.
| Song content | Tag written |
|---|---|
| Title | {title: Amazing Grace} |
| Artist, or the composer if there is no artist | {subtitle: John Newton} |
| Comment | {c: Play softly} |
| Verse | A name line such as {c: Verse 1} |
| Chorus | {start_of_chorus} and {end_of_chorus}, with no name |
| Tab | {start_of_tab} and {end_of_tab}, with the name, if any, written as a {c: …} line before them |
A section is exported as a chorus only when it is named exactly “Chorus”, ignoring capital letters. Any other named verse section, including a translated “chorus”, is written as a verse, with its name as a {c: …} line.
ChordPro v4.6 files are saved in the ISO Latin-2 character set. Characters it cannot represent, such as ã, õ, curly quotes and non-Latin scripts, are replaced with ?. Use ChordPro v5.0 for songs with these characters.
Setlist export
Export setlist to ChordPro
- From the setlist view, open the Share Sheet and select Export As.
- Choose to export the setlist as ChordPro format.
- Send the setlist via AirDrop, choose an app to open the ChordPro file in, copy to clipboard, or save it to Files.
The file starts with a summary, followed by the songs:
- Two comment lines: the setlist name, and a “Created using SongSheet” line with the website address. The wording of the second follows the app’s language.
- A
{title: …}tag with the setlist name. - One list per set, with a
{c: …}line giving the set’s name (left out when the setlist has a single set with the default name), then oneTitle (Artist)line for each song. - Each song once, even if it appears in several sets, in ChordPro v5.0 format and starting with a
{new_song}tag.
SongSheet Pro can’t import this layout back as a setlist (see Setlist files).
SongSheet Pro