Chordleaf

Support

Email maga40@naver.com. Include your version, device model and the operation that failed. Share song content only if you choose and have permission.

Write or import

  1. In Songs, create a new song or explicitly add the three original demos.
  2. Place [G] before a syllable, use {comment: Chorus} for headings and [*Coda] for literal annotations.
  3. Import a UTF-8 .cho, .chordpro, .chopro, .pro or .txt file under 2 MB. Inspect its source and save it.
  4. Open Key for semitones and accidentals. Reading controls text size, serif/mono, night paper and print settings.
  5. Use Export for the actual PDF, retained original source or arranged ChordPro.

Supported music text

A conservative subset of common letter chords, extensions, C6/9-style numeric suffixes and slash bass chords is supported. Unknown bracket tokens remain unchanged; explicit asterisk annotations are not transposed. Unsupported directives remain visible and appear in editor notes. There is no playback, chord diagram library, notation engraving, MIDI, licensed catalog or full ChordPro implementation.

Set keys and printing

Create a set, add songs and use Up/Down or Edit to reorder. Open its song and choose Key to save a set-only arrangement. Use master arrangement resets that override. The PDF follows the set order and arrangements. Choose A4 or US Letter and 10–18 pt print size in Reading. Screen night mode and device text size do not affect print size.

Backup and limits

Files exports a library JSON or ZIP with current sources, exact retained imported bytes and set CSV files. Restore the JSON, not the ZIP, through Restore copies from JSON. Copies receive new IDs and their sets are remapped; existing songs are not overwritten. New additions allow 200 songs and 40 sets. Backups must be under 64 MB. Reading/printing limits are 120,000 characters and 2,400 source lines per song; larger source stays editable and exportable. CSV cells that could start a spreadsheet formula receive a leading apostrophe; JSON retains the original text.

Storage recovery

Write errors keep the prior saved state and show an error. An unreadable saved library is protected. Export original library file, then explicitly select a valid JSON replacement. The app also preserves a separate copy of the unreadable file before replacement. There is no developer cloud recovery. Export important work outside this device before deleting the app.