If you have collected chord sheets for any length of time, you have a folder of text files that all look the same: a line of chord names, then the words underneath, the two held together by a row of spaces. It is the oldest format on the internet and it works perfectly until the moment anything about the display changes.

Converting that to ChordPro takes one paste. What follows is what the conversion is doing, so you can tell when it has got it wrong.

Convert a chord sheet in four steps

  1. Copy the whole sheet, chord lines and lyric lines together. The blank lines between verses can come too — they mark the sections and survive the conversion.
  2. Paste it into the free ChordPro converter. It runs in your browser: nothing is uploaded, nothing is stored, and there is nothing to sign up for.
  3. Read the output, which appears as you paste. The check takes five seconds and is described below.
  4. Copy it back out, or download it as a .chopro file. That file is plain text and yours.

That is genuinely the whole procedure. The rest of this article is about the part nobody tells you: the conversion is a guess, and you should know which guess it is making.

What changes, exactly

Here is a sheet in the format almost everything is published in:

Am                   F
The last bus home is late
         C          G
and I am singing anyway

And the same thing as ChordPro:

[Am]The last bus home is [F]late
and I am [C]singing any[G]way

The chord names have not changed and the words have not changed. What changed is what the chord is attached to. In the first version F is at column 21 and happens to have "late" underneath it. In the second it is in the line, immediately before the word it belongs to.

That is the whole idea, and every useful thing follows from it. A chord tied to a syllable can be transposed, capo'd, reflowed on a phone, or reprinted at any size, and it stays over the word it was always over. A chord tied to column 21 survives none of those — change the font, open it on a narrower screen, let one long line wrap, and every chord slides away from the word it belonged to.

The guess the converter is making

To convert a sheet, something has to decide which lines are chords and which are words. There is no marker — both are just text.

The rule is: a line is a chord line if every token on it parses as a chord name. That gets it right nearly always, and nearly is the interesting part. A line reading A on its own could be a chord or the first word of a sentence. A line of Do Re Mi is three chords in Italian notation and three syllables in English.

So the conversion is a heuristic. It is a good one, and it will still be wrong on some sources — which is why the converter shows you the output instead of handing you a file, and why the import screen inside the app keeps the converted song editable before it saves anything.

The bias is deliberate and worth knowing, because it decides which way the mistakes fall: a chord line mistaken for lyrics leaves a stray line you can see and fix, while lyrics mistaken for chords take words out of the song and hide them above an unrelated line. Given the choice — on a line of bare note names like do re mi — the converter takes the first. A lone A on its own line is still read as a chord, so that is the line to check.

How to check it in five seconds

Read the output and look at where the brackets landed. You are checking one thing: is each chord immediately before the syllable you actually change hands on?

The failure has a signature. A misaligned source produces brackets inside words — hom[F]e, sing[C]ing — because the chord's column fell in the middle of a word rather than at its start:

Am                 F
The last bus home is late
[Am]The last bus home i[F]s late

A column or two of drift in the input is a misplaced bracket in the output. The fix is in the input, not the output: nudge the chord line left or right until the chord sits over the first letter of the word, and paste again. Fighting the result instead means fixing the same thing once per verse.

Things that are not chord sheets

A few kinds of file look close enough to confuse a converter and are worth knowing about:

  • Tab. Six lines of e|---3---0--- are not chords above words, and converting them as if they were produces nonsense. A good converter leaves tab rows alone; this one does.
  • Lyrics with no chords at all. Nothing to convert — the words come through unchanged, which is the right answer rather than an error.
  • Something already in ChordPro. Also nothing to do. The converter says so instead of bracketing the brackets.
  • A chord chart with bar lines, | Am | F | C |. The bars are not chord names, so the converter does not read the line as chords at all: it comes back exactly as you pasted it, which is the honest answer — there was never a syllable under those chords to attach them to.

More than one song in the paste

ChordPro separates songs with a {new_song} directive; Strumfolio also splits on a second {title: …} and on a line of --- between pasted songs — which means a file holding a whole songbook comes apart on those boundaries. If you paste several songs at once, the converter will say how many it found, and importing the same paste into Strumfolio splits them into separate songs rather than one very long one.

What to do with the file afterwards

A converted sheet is a .chopro file, and it is worth treating as a document rather than a clipboard step:

  • Keep it somewhere you back up. It is plain text — a folder in a cloud drive, a git repo, an email to yourself. Any of those outlives any app.
  • Name it after the song, not the source. the-last-bus-home.chopro beats ug-tab-copy-3.txt the first time you look for it in a hurry.
  • Open it in something that reads ChordPro to see the chords land over the right syllables at any size. That is the point of the conversion, and it is only visible once something renders it.
  • Transpose it after converting, not before. ChordPro survives a key change exactly; the column layout barely does — the chord transposer will move a whole sheet either way and tell you when a column could not be kept.

A note for people leaving another app

If your sheets came out of OnSong, MobileSheets or SongbookPro, they may already be ChordPro — but in that app's own dialect, where the same directive means different things. {a: …} is the artist in OnSong and the album in MobileSheets. {st: …} is a subtitle in the specification and was redefined by OnSong to mean the artist.

Read with the wrong table, each of those puts a correct value under the wrong heading, silently. A wrong value that arrived quietly is worse than a missing one, because nothing ever prompts you to look at it again. It is worth checking that whatever you import with knows the difference — Strumfolio's importer does, and refuses to guess when nothing identifies the source.

Where the apps disagree, the specification is the thing to settle it against: the official ChordPro cheat sheet is a single page listing the directives you will meet day to day, which is usually shorter than the list your old app was writing. Anything on that page is safe to keep; anything that is not is worth checking against the reference implementation before you call it a dialect.

Why bother at all

Because the file outlives the app. A .chopro file is plain text: it opens in any editor, it goes into version control, and it will still be readable when the app you typed it in has changed hands or names or gone. That argument is worth its own article, and it has one.

Questions people ask

How do I convert a chord sheet to ChordPro?
Copy the sheet with its chord lines and lyric lines together, paste it into a converter, and read the output before you keep it. The free ChordPro converter on this site does it in the browser with nothing to sign up for and nothing uploaded. The whole job is one paste; the part worth your attention is checking that each chord landed immediately before the syllable you change hands on.
What is ChordPro format?
A plain-text format for lyrics and chords in which the chord is written inside the line, in square brackets, at the exact point in the word where your hand changes — [Am]like this. Lines in curly braces are directives holding the title, the key, the capo and so on. Because a chord is attached to a syllable rather than to a column of spaces, the sheet can be transposed, capo’d and reflowed on any screen without anything drifting.
Does converting change my chords?
No. The chord names and the words come through untouched — the only thing that changes is what each chord is attached to. If a chord name comes out different from what you pasted, that is a misread rather than a conversion, and it will be visible in the output because the converter shows you the result instead of saving it.
Can I convert a whole songbook at once?
Yes, if the songs are separated by a `{new_song}` directive, a second title directive or a line of `---`, which is how a multi-song file marks where one song ends. The converter reports how many songs it found in the paste, and importing that same paste into Strumfolio splits them into separate songs rather than one very long one. A paste with none of those converts as a single song.