ChordPro in Setliner™
The lines Setliner™ reads, what each one does, and what it ignores.
ChordPro is a text format for chord charts. Setliner™ reads a part of it, and it adds a few lines of its own. This page lists each line Setliner™ reads, what it does on screen, and what Setliner™ ignores or shows as plain text.
The list comes from the code that reads ChordPro in Setliner™ 2.4.0. It was checked on 2026-11-18. Setliner™ is not affiliated with the ChordPro project.
How to read this page
Each line has one of four statuses.
- Supported. Setliner™ reads the line and uses it.
- Shown as text. The line appears in the chart as plain text.
- Ignored. Setliner™ does not show the line and does not use it. It keeps the line in the song’s text and writes it back when you export the song.
- Changed on export. Setliner™ uses the line, but a
.chofile that Setliner™ exports spells it in a different way.
Tell us through the contact page if you find a line that does not do what this page says.
File types
- Import:
.cho,.chordpro,.chopro,.pro,.crd,.chordand.txt. The list is the same on Windows, macOS, Linux and Android. PDF charts have their own import and are not covered here. - A
.txtfile: on Windows, macOS, Linux and Android, Setliner™ reads it as ChordPro if it has a ChordPro line that Setliner™ reads, or a chord in square brackets. If it does not, Setliner™ reads it as a “chords above lyrics” chart. - Several songs in one file: put
{new_song}or{ns}on its own line between the songs. Setliner™ imports each part as one song. - Export: a ChordPro export is a
.chofile. The app also exports plain text, PDF, Word and Setliner™’s own format. - Round trip: a file from another app comes back byte for byte when you import it and export it again without changes. Setliner™ keeps the line endings, the lines it ignores and the remark lines.
How a line is written
- A directive looks like
{name: value}. The colon is optional:{sov Verse 3}works. Capital letters in the name are fine. A name has only letters and underscores. - Put one directive on its own line. If other text shares the line, Setliner™ shows the line as lyrics. Two directives on one line are not read as two directives. The only exception is the note and comment family, which can sit inside a lyric line (see Comments and notes).
- Remark lines. A line that starts with
#in the first column is a remark. Ignored. It is not shown on stage. A#after a space is lyric text. - Empty lines. Supported. An empty line stays and adds space in the chart.
- Tags for one instrument. A name with an instrument tag, such as
{textcolour-piano: red}or{title-piano: Piano title}, is ignored. There are three exceptions. The start and end lines of a section are read:{start_of_verse-piano}is a normal verse. A tag with!, which means everyone except that instrument, is read:{c-guitar!: everyone but guitar}is a note.{define-guitar: …}is read, and{define-ukulele: …}is not. - Attributes. A section line can give its name as
label="Chorus 2"orlabel='Chorus 2'.
Song details
Put these lines at the top of the file. A song that you write in the app has the same details in its own fields.
{title: …}or{t: …}. Supported. The song title.{subtitle: …}or{st: …}. Supported. The other name of the song. It is not the artist. Use{artist: …}for the artist.{artist: …}. Supported.{copyright: …}. Supported. Saved as the song’s copyright line.{key: G}. Supported. The key that the chords are written in. Transposing starts from this key.{tempo: 90}. Supported. Beats per minute, as a whole number. Setliner™ drops a value such as92.5. Practice, an optional feature, counts in and keeps time with the tempo and the time signature.{time: 3/4}. Supported. The beats in a bar, saved as you write it.{capo: 2}. Supported. The capo fret, as a whole number.{tags: hymn, communion}or{tag: hymn}. Supported, changed on export. A comma list, or one tag on each line. A tag that the song already has is not added twice, and capital letters do not make a new tag. Setliner™ exports one{tag: …}line for each tag.{about: …}. Supported, changed on export. It becomes the song’s notes. Setliner™ exports it as{x_setliner_about: …}.
Other detail lines, such as {album}, {composer}, {lyricist}, {year}, {sorttitle}, {duration} and {meta: …}, are ignored.
Sections
A section label starts a new section in the chart. Setliner™ gives each section a color and lets you collapse it.
Heading lines
- A line that holds only a section word is a label. Supported. The words are Verse, Chorus, Pre-Chorus, Post-Chorus, Bridge, Intro, Outro, Ending, Tag, Interlude, Instrumental, Tab, Turnaround and Solo. Capital letters do not matter.
- A number or a letter can follow the word, for example
Verse 2. - These forms all work:
Chorus,[Chorus],(Chorus)andChorus:.
Setliner’s own section line
{section: Modulation}or{s: Modulation}. Supported, changed on export. The name can be any text. This line is not part of ChordPro. When you export, Setliner™ writes{start_of_…: Modulation}and an end line instead. A name that is not a known section word is written withstart_of_verse.
Section directives from other apps
These start lines are supported. Each one makes a section label.
{start_of_chorus}or{soc}{start_of_verse}or{sov}{start_of_bridge}or{sob}{start_of_tab}or{sot}{start_of_grid}or{sog}{start_of_intro},{start_of_outro},{start_of_ending},{start_of_instrumental}and{start_of_interlude}{start_of_prechorus}or{start_of_pre_chorus}{start_of_postchorus}or{start_of_post_chorus}
- Name. Add a name after a colon:
{start_of_chorus: Big Chorus}. The newer form works too:{start_of_chorus label="Chorus 2"}. - Numbers. Without a name, Setliner™ numbers the first five (chorus, verse, bridge, tab and grid) by type. Three plain
{sov}blocks become Verse 1, Verse 2 and Verse 3. The other types are not numbered. - End lines.
{end_of_chorus},{eoc}and the matching end lines close a section. They add nothing to the chart. - Other names. A start line with a name that is not in the list, such as
{start_of_solo}, is ignored. The lines inside it are shown as normal lines. Write{section: Solo}instead. - Chord grids.
{start_of_grid}makes a section. The rows inside are shown as text. A grid shape, such as1+4x2+4, is not used as the name. - Tab blocks.
{start_of_tab}makes a section. The rows inside are shown as text.
Repeat a chorus
{chorus}. Supported. It repeats the last chorus that ended with{end_of_chorus}or{eoc}, under the same heading.{chorus: Final}or{chorus label="Final"}gives the repeat its own heading. If no chorus has ended yet, only the heading appears. A{new_song}line clears the last chorus.
Comments and notes
{comment: …},{c: …},{comment_italic: …},{ci: …},{note: …}and{n: …}. Supported. Each one makes a small italic note in the chart at the place where you put it. It is not a section label. This is true when the text is a section word:{comment: Chorus}is a note. Add a heading line if you want a section.- Inside a lyric line. The same six names can sit inside a lyric line, before the word they belong to:
[G]{note: softly}grace. - Changed on export. Setliner™ exports
{note: …}as{comment: …}. {comment_box},{cb}and{highlight}are ignored.- Text styling. Tags such as
<b>,<i>,<u>and<span …>are not drawn. Setliner™ shows the words without the tags in lyrics and in{comment},{c}and{ci}lines. A{note}or{n}line shows its tags as written. The file keeps the tags.
Chords in brackets
- Inline chords. Put the chord in square brackets before the syllable that it starts on:
[G]Amazing [C]grace. Supported. - Chord names that move. Setliner™ changes a name when you transpose if it has a root from A to G, an optional
#orb, a quality such asm,7,maj7,sus4oradd9, and an optional bass note after a slash, such asD/F#. - Other text in brackets. Setliner™ accepts any text up to the closing bracket as a chord slot. A slot that is not a chord name is shown as you wrote it and does not move. Examples:
[|](a bar line),[x2](a repeat count),[N.C.](no chord) and[riff]. Practice skips these marks. To play a whole section more than once, add a repeat to the song’s sequence, such as Chorus (x2). Setliner™ shows the count beside that section. - Optional chords. Put the chord in parentheses:
[(Aadd9)]. Setliner™ shows it as written, and it moves when you transpose. In Practice (desktop), an optional chord is right when you play it. If you leave it out, the highlight moves on when you play the next chord, and the chord is never marked missed. Another chord played there is still wrong. A chord in parentheses that repeats the chord before it, as in[A]still [(A)]here, is only a reminder: it is the same A, one chord to play. - Annotations.
[*Rit.]is shown as a small note above the lyric, like a{note}. It does not move when you transpose. A lone[*]stays a chord slot. - Hammer-on and pull-off.
[h]and[p](and[*h]and[*p]) are read as marks, not as chords. - Nashville numbers. A chord such as
[4]or[6m]is not a chord name in the file. Setliner™ shows it as written, and it does not move when you transpose. On Windows, macOS, Linux and Android, the song editor can change number chords into letter chords if the song has a{key}. Setliner™ keeps letter names in the file. The Nashville setting only changes how the chart is drawn. The conversion rules: the written{key}is the frame (never a capo, a transposition or a detected key); a degree is a number from 1 to 7 with an optional#orbin front, then a quality, then an optional slash and a second degree (1/3); a dash reads asm; in a minor key the numbers count from its own tonic;3b,8and0are refused (writeb3); letter chords and marks such asN.C.,|andx2are never changed. With no readable key, nothing is converted. - Escapes in lyrics and chords. A literal
[,],{or%in a lyric is written%5B,%5D,%7Bor%25, and Setliner™ reads those back. A lyric that really starts with#is written%23so it is not taken for a remark. A doubled bracket, such as[[mute]], is a chord slot that holds the text[mute]. A written\u005Bis read as[, and any\uXXXXcode (four hex digits) is read as that character. - A bracket without a closing bracket is not a chord. The text stays as plain text.
Links, blackout, chord shapes and tabs
{video: https://…}. Supported, changed on export. It adds a link to the song. Use one line for each link. The link can be a web address or a file path. Setliner™ exports it as{x_setliner_video: …}.{youtube: https://…}. Supported, changed on export. The older single-link form of{video}. Use{video}for new links.{x_chordle_weblink: https://…}near the top of a file becomes a link too.{blackout}, or a line that has only the word blackout. Supported, changed on export. It marks a point in the song as a “go dark” cue. The bare word, with or without brackets or parentheses, works too. When a display’s viewer scrolls to a section that holds only this marker, every connected screen blanks, unless that monitor has “obey blackout” turned off (this uses the optional display features). Use it for a silent section or a prayer. Setliner™ exports the directive as{x_setliner_blackout}. The bare word is kept as written.{define: Asus4 base-fret 1 frets x 0 2 2 3 0}. Supported for a guitar chord with six strings. It becomes the song’s saved shape for that chord. Setliner™ keeps keyboard chords, chords for other string counts, finger numbers and copy lines in the text only (ignored).{new_song}or{ns}. Supported. It splits a file into songs (see File types).- Tab lines that you type, such as
e|---0---|, are kept as you typed them. On all apps, the viewer can offer to turn them into a tab.
What Setliner™ ignores
Setliner™ does not show these lines and does not use them. It keeps them in the song’s text and writes them back on export.
- Page and layout:
{columns},{column_break},{new_page},{new_physical_page},{pagetype},{titles}and{grid}. - Fonts, sizes and colors:
{textfont},{textsize},{textcolour},{chordfont},{chordsize},{chordcolour}and the other font lines. Setliner™ draws the chart in its own skin. - Pictures:
{image: …}. - Transpose:
{transpose: 2}. Setliner™ does not apply it. Use the transpose control in the app. - Chord lines:
{chord: …}and keyboard{define}lines. - Embedded blocks:
{start_of_abc},{start_of_ly}and similar blocks. The lines inside them are shown as normal lines. - Detail lines: album, composer, lyricist, year, sorttitle, duration and meta (see Song details).
- Any other directive that this page does not list.
A song file with several songs is handled in File types.
Setliner’s own directives
These lines and spellings are not part of standard ChordPro, or Setliner™ gives them its own meaning. Each item says what other apps read when you export a .cho file.
{section: Name},{s: Name}. Supported, changed on export. A section label with any name. Export:{start_of_…: Name}and an end line. Other apps read it. A name that has no known section type usesstart_of_versewith the label. A label that cannot be written that way is exported as{x_setliner_section: …}.{note: …},{n: …}, on its own line or inside a lyric line. Supported, changed on export. A small italic note. Export:{comment: …}. Other apps read it. A note that holds a line break is exported as{x_setliner_note: …}.{tags: a, b}. Supported, changed on export. Export: one{tag: …}line for each tag. Other apps read it. In a tag list, a comma that belongs to the tag is written%2C.{blackout},{about: …},{video: …},{youtube: …}. Supported, changed on export. Export:{x_setliner_blackout},{x_setliner_about: …},{x_setliner_video: …},{x_setliner_youtube: …}. Other apps ignore them.{section_tab: …}to{end_of_section_tab}, with{tab_label},{tab_bars},{tab_tuning}and{tab_source_indent}between them. Supported, changed on export. A tab made in the tab editor. Export: each name gets the prefixx_setliner_. Other apps ignore the block.[h]and[p]. Supported, changed on export. Hammer-on and pull-off marks. Export:[*h]and[*p]. Other apps show them as annotations. Setliner™ reads both spellings.[(Aadd9)],[|],[x2],[N.C.]. Supported. Optional chords and chord-row marks (see Chords in brackets). Export: written as they are.- A heading line such as
Chorusor[Verse 2], and a line with only the word blackout. Supported. Other apps show them as lyric text. Export: written as they are. {x_setliner_recording_note: …}. Supported. The song’s recording note. Other apps ignore it.{x_setliner_midi: …}. Supported. The MIDI messages that the song sends when you move to it. Other apps ignore it.{x_setliner_practice_timing: …}, one line for each saved timing. Supported. Practice data. Other apps ignore it.{x_setliner_fill: …}, one line for each fill. Supported. A fill that Practice saves at one place in the song. Other apps ignore it.{x_setliner_song: …}. Supported. The last line of an exported file. It holds what the text cannot hold (see What Setliner™ writes). Other apps ignore it. Setliner™ reads it back when you import the file.{x_chordle_weblink: https://…}. Supported. Chordle’s own link line. Setliner™ reads it at the top of a file as a video link. Otherx_chordle_…lines are ignored.- Percent codes in the values that Setliner™ writes. Supported. They keep a value on one line:
%7Dis},%0Ais a line break,%0Dis a carriage return and%25is%. At the start or end of a value, a space is%20and a tab is%09. Setliner™ reads these codes in the title, subtitle, artist, copyright, key, time, video, section, note and about values. It does not read them in{youtube}or in{comment}lines. - Number chords such as
[4](Nashville entry). Shown as text until you convert them in the song editor on Windows, macOS, Linux or Android (see Chords in brackets). Setliner™ never writes a number chord to the file.
Saved with the song, not in the text
Setliner™ keeps these with the song file next to the chart. They are not ChordPro lines, so you do not see them in the text. An export puts them in the {x_setliner_song} line.
- Sequences, such as Verse 1 and Chorus (x2).
- Saved chord shapes and chord overrides, and the song’s tuning.
- Drawings, and the last view settings.
- Section colors come from each section’s name and your color settings.
- Optional parts of a sequence. Put a part you may or may not play in square brackets.
[Bridge, Chorus x2]is one part, taken or skipped together.[Bridge], [Chorus x2]are two parts, each on its own. On stage, tap the part on the sequence strip to take or skip it. On desktop you can also use the toggle shortcut, which is the O key by default. On Android you can use the cue button of the pedal. Follow mode, the next section and the other displays go straight past a skipped part. Settings choose whether optional parts are played until you skip them, or skipped until you take them. Practice listens for whether you played the part and never counts a skipped one as missed.
What Setliner™ writes
In your songs and exports
- A song that you write in Setliner™ starts with detail lines (title, subtitle, artist, copyright, key, tempo, time, capo, tags, links and notes). Then come the chart lines. Setliner™ writes
{section: …}for a section,{note: …}for a note and{blackout}for a blackout cue. - When you export a song as ChordPro, Setliner™ writes the song’s own text and changes only the lines that no other app reads. These lines change:
{section: Verse 2}becomes{start_of_verse: Verse 2}and an{end_of_verse}line.{note: …}becomes{comment: …}.{tags: a, b}becomes{tag: a}and{tag: b}.[h]and[p]become[*h]and[*p].{blackout},{about},{video}and{youtube}get the prefixx_setliner_. The lines of a Setliner™ tab block get it too.
- ChordPro asks that a custom directive starts with
x_. Other ChordPro apps ignore these lines.
Lines that only Setliner™ writes
{x_setliner_song: …}. One last line in an exported.chofile when the song has data that text cannot hold: sequences, saved chord shapes, view settings and drawings. Keep this line if you want to import the song into Setliner™ again with all of its data. If another app edits the text, Setliner™ uses the edited text and puts the extra data back. If you delete the line, Setliner™ still reads the standard lines. It also still reads the recording note, the MIDI line and the Practice data, because it reads them from the text. It does not read back the lines that it renamed (x_setliner_about,x_setliner_video,x_setliner_youtube,x_setliner_blackout,x_setliner_section,x_setliner_noteand the tab lines), and the extra data is lost.{x_setliner_recording_note: …}. The song’s recording note.{x_setliner_midi: …}. The MIDI messages that the song sends when you move to it.{x_setliner_practice_timing: …}and{x_setliner_fill: …}. Data that the optional Practice feature saves with a song.{section_tab: …},{tab_label},{tab_bars},{tab_tuning},{tab_source_indent}and{end_of_section_tab}. A tab that you make with the tab editor. Change it in the tab editor, not by hand. A block that Setliner™ cannot read is shown as plain text.- In the values that it writes, Setliner™ spells a few characters as codes, so a value stays on one line:
%7Dfor},%0Afor a line break and%25for%.
Setliner™ saves some data with the song and not as ChordPro lines: sequences, saved chord shapes, the song’s tuning, drawings and the last view settings. An export puts them in the {x_setliner_song} line.
Common mistakes
- The sections of a chart from another app show as notes. Some apps write sections as
{comment: Chorus}. Setliner™ reads every comment as a note. Add a heading line, or change the line to{section: Chorus}. - A directive shows as lyric text. Other text is on the same line. Give the directive its own line.
- A title or a section name shows braces. Two directives are on one line, such as
{t: A}{st: B}. Setliner™ reads the text from the first brace to the last brace as one value. Put each directive on its own line. - The artist shows as a second title. The file has the artist in
{subtitle}. Change it to{artist: …}. - The tempo or the capo is missing. The value is not a whole number. Write
{tempo: 92}, not{tempo: 92.5}. - A chord does not change when you transpose. The text in the brackets is not a chord name. Examples are
[4],[riff]and[x2]. Write the chord with a letter, such as[G]. - Text stays in the lyrics with its brackets. A bracket has no closing bracket. Close it with
]. - A remark shows on the chart. The
#is not in the first column. Remove the spaces before it. - A section is missing. The start line is not in the list, for example
{start_of_solo}. Use{section: Solo}.
Examples
Copy a text block into a plain-text file. Save it with the ending .cho. Then import the file.
1. A small song
{title: Amazing Grace}{artist: John Newton}{key: G}{tempo: 90}{time: 3/4}{capo: 2}{tags: hymn, communion}
{start_of_verse}[G]Amazing [C]grace how [D]sweet{end_of_verse}
{start_of_chorus}[G]La la [C]la{end_of_chorus}
Result: the title, the artist, the key G, 90 beats per minute, 3/4 time, capo 2 and two tags. The chart has the sections Verse 1 and Chorus 1.
2. Notes, a repeated chorus and special chords
# Only for the person who keeps this file{title: Example Two}
{sov}[G]Amazing [*Rit.]grace [(Aadd9)]how [D]sweet{c: softly}{eov}
{soc: Refrain}[G]Sing it [C]out [x2]{eoc}
{chorus}
Result: the first line is not shown. Verse 1 has a small note above “grace” (Rit.), the optional chord Aadd9 and the note “softly” under the line. The chord [x2] is shown as written. The section Refrain appears again at the end with the same lines.
3. Two songs in one file, with a chord shape
{title: First Song}{key: C}[C]La [G]la{new_song}{title: Second Song}{define: Asus4 base-fret 1 frets x 0 2 2 3 0}[Asus4]Lo [D]lo
Result: Setliner™ imports two songs. The second song keeps the shape for Asus4.
Back to the FAQ, or download Setliner™.