forSheets (and giggles)

About forSheets

forSheets converts setlists between forScore (.4ss files) and MobileSheets (.mss setlist files) in both directions, preserving song titles and PDF filenames so either app can match entries against the library already on your tablet.

Why it exists

forSheets started the unglamorous way: retyping a long wedding setlist a second time, by hand, after switching tablets — then discovering both apps already export an open setlist format and nothing reads the other's. So it was built to bridge exactly that gap: share the setlist out of one app, convert it here, import it into the other. The native forScore format (a gzip-compressed binary plist with parallel song/file arrays and no stored setlist name) was worked out by reverse-engineering a real export, and every change since has been tested against real gig setlists the week it was needed.

How it works

Conversion is handled by a small, dependency-free engine that runs entirely in your browser: files normalize into a neutral setlist of score, bookmark, and placeholder entries, and the other side is generated from it. Files are read with local file APIs and converted in memory; nothing is uploaded, stored, or shared (see Privacy).

What it deliberately does not do

• No .msf song files or .msb library backups — those are proprietary MobileSheets bundles. Export the setlist as .mss instead.
• No uploads, accounts, or cloud library — the public site is static and the conversion never leaves your device.
• No page-turn or annotation conversion — only setlist structure (titles, filenames, PDF payloads) crosses over.

Free and private

forSheets is free and runs entirely in your browser — no accounts, no uploads, no paywalls. The site stays up through Google AdSense ads — there are no premium tiers and no feature gates. Bug reports and setlist edge cases are welcome at help@forsheets.app (see Contact for what to include).