How to Import Sheet Music from Google Drive

If your choir, band, or personal music library lives in a Google Drive folder full of PDFs, the thought of moving it to a dedicated system can feel daunting. You've got hundreds (sometimes thousands) of scores, each one a share link that could take an afternoon to upload by hand.

MusicLib's CSV import wizard has a feature built exactly for this situation: map one of your columns to a Google Drive Link field, and MusicLib will fetch every PDF from Drive automatically in the background. You paste one CSV, walk away, and come back to a fully populated library.

Here's how to set it up.

Before You Start: What You'll Need

• A Google Drive folder containing your score PDFs.
• A spreadsheet (Google Sheets, Excel, or anything that can export CSV) listing the titles and any metadata you want to keep: composer, voicing, genre, call number, etc.
• A MusicLib account. The free tier supports up to 50 scores; larger libraries need a Pro or Organizations plan. You can compare plans here.

If your spreadsheet doesn't already have a column with Drive links in it, you'll add one. That's the one piece of prep work that matters.

Step 1: Make Your Drive Files Shareable

This is the single most important step, and the one most people trip on. MusicLib downloads each PDF over HTTPS using its public share URL. For that to work, the files must be shared as "Anyone with the link".

You can set this at the folder level (easiest, applies to every file inside) or on individual files:

1. Open your Drive folder.
2. Right-click the folder (or an individual file) and choose Share.
3. Under General access, change "Restricted" to "Anyone with the link".
4. Make sure the role is set to Viewer, then click Done.

If you're worried about your library being publicly discoverable: the "Anyone with the link" setting doesn't make files searchable on Google. It only means that someone who has the exact URL can view the PDF. And because MusicLib stores its own copy once imported, you can re-lock the Drive folder the moment the import finishes.

Step 2: Build Your CSV

Your spreadsheet needs one row per score. At minimum include Title and Google Drive Link. Everything else is optional but worth populating while you're at it — the time you spend cleaning up metadata now is time you don't spend hunting for pieces later.

A simple CSV looks like this:

Title,Composer,Voicing,Genre,Drive Link
Ave Maria,"Bach, J.S.",SATB,Sacred,https://drive.google.com/file/d/1AbCdEf.../view
Hallelujah Chorus,Handel,SATB,Sacred,https://drive.google.com/file/d/1XyZ123.../view
Simple Gifts,Copland,SSA,Folk,https://drive.google.com/file/d/1PqRsTu.../view

Don't worry about the exact column names — the wizard will let you map "Drive Link" (or whatever you called your column) to MusicLib's Google Drive Link field in the next step.

If you already have your library tracked in a spreadsheet, you don't need to start from scratch — just add a Drive Link column and export it to CSV. Every common spreadsheet program can do this:

• Google Sheets: File → Download → Comma-separated values (.csv).
• Microsoft Excel: File → Save As → choose "CSV UTF-8 (Comma delimited)".
• Apple Numbers: File → Export To → CSV.
• LibreOffice Calc: File → Save As → File type "Text CSV (.csv)".

Any of these formats work — MusicLib accepts a plain UTF-8 CSV.

Step 3: Run the Import Wizard

In MusicLib, go to Import / Export and click Import Scores from CSV. Then:

1. Upload your CSV. The wizard parses it and shows you every column it detected.
2. Map your columns. The wizard auto-maps obvious columns (Title → Title, Composer → Composer). For your Drive URL column, pick Google Drive Link (auto-download PDF) from the Special group in the dropdown. This is the one that triggers the automatic download.
3. Preview and clean up. The wizard shows a table of every row with any validation errors highlighted. Fix typos, delete rows you don't want to import, and move on.
4. Confirm and run. MusicLib creates all the score records immediately. PDFs start downloading from Drive in the background.

The import itself is fast — even 1,200 rows of metadata are created in under a minute. What takes longer is fetching the PDFs. A few minutes for 50 files, maybe an hour for 1,200. You can close the browser tab; MusicLib keeps downloading.

Step 4: Handle Failures (If Any)

If some files weren't shared as "Anyone with the link" — or a link is broken, or a file is larger than 250 MB — MusicLib can't fetch them automatically. When the downloads finish, if any failed, you'll see a notification in the toolbar bell:

"12 PDFs failed import from Drive."

Click it. A modal pops up grouping the failures by reason, with step-by-step instructions for each. The most common cause is private sharing — fix the permissions in Drive, click Retry all, and MusicLib re-attempts every failed download. Successful retries silently drop off the list.

This is the loop we recommend for large migrations:

1. Run the import.
2. Wait for the failure notification.
3. Fix the sharing on the flagged files in Drive.
4. Click "Retry all."
5. Repeat until the notification disappears.

Most libraries land within one or two retry cycles.

What Happens After Import

Once a PDF is attached to a score, MusicLib automatically:

• Generates a thumbnail so your library browses visually.
• Runs OCR (Pro tier) so the text inside the PDF becomes searchable — handy for finding that Bach motet when you can only remember a lyric fragment.
• Stores its own copy. You don't need to keep the Drive folder shared, or even keep the Drive folder at all.

From here you can start building collections, setlists, and checkout tracking on top of what's now a proper searchable library. See our guides on organizing sheet music for a choir, organizing for orchestra, or cataloging best practices.

Common Questions

Can MusicLib download from private Drive files I own?

Not currently. Every file has to be shared as "Anyone with the link" for the duration of the import. You can re-lock the folder immediately after the imports succeed. Support for OAuth-based private Drive access is on our roadmap.

What about files larger than 250 MB?

The import has a 250 MB per-file cap to protect server disk during bulk imports. For rare oversized scores — like a full orchestral score scanned at high resolution — upload them manually from the score's detail page after the import.

Does this work with Dropbox, OneDrive, or iCloud?

Google Drive is the only cloud source supported today. If you'd like another provider, let us know at info@musiclib.net.

What if my CSV is massive?

The wizard handles up to 10,000 rows per import. If you have more, split your spreadsheet into batches. Drive downloads happen asynchronously, so you can kick off batch two while batch one is still fetching PDFs.

A Real-World Example

A professional choir we recently onboarded had about 1,200 PDFs in a Google Drive folder along with a Google Sheet tracking titles, composers, and voicing. Total time:

• 15 minutes to flip the folder to "Anyone with the link" and export the Sheet to CSV.
• 2 minutes in the import wizard to map columns and confirm.
• About 40 minutes for MusicLib to fetch all 1,200 PDFs in the background (while they went to lunch).
• 10 minutes to resolve a handful of files that hadn't inherited folder permissions, using the "Retry all" button.

Total hands-on time: around 30 minutes to migrate 1,200 scores. No click-and-upload, no manual file naming, no lost work. That's what this feature was built for.