What is a .jwlibrary file — and how to open one on any device
A .jwlibrary file is your JW Library backup: a single file holding every note, highlight, bookmark and tag. Here's what's inside it and how to open and read it.
A .jwlibrary file looks opaque, and it is not. It is an ordinary ZIP archive around an ordinary SQLite database, which means you can read your own backup — see exactly which notes, highlights and bookmarks it holds — without JW Library and without installing anything at all.
When you back up JW Library you get a file ending in .jwlibrary. It's a single, portable package that contains everything from your personal study — notes, highlights, bookmarks, tags and playlists — in a compact database. It is not a document you open in Word or a PDF reader; it's designed to be restored back into JW Library.
But you don't have to restore it just to look inside. JW Sync opens a .jwlibrary file directly in your browser so you can read, search and edit its contents without touching your phone.
Step by step
Get a .jwlibrary file
It's created in JW Library: Personal Study → three-dot menu → Backup and Restore → Create a backup. That's the file we're talking about.
Open it in JW Sync
Go to jwsync.org and load the file into Study Explorer. It opens instantly, on your device — nothing is uploaded.
Read and work with it
Browse notes, highlights and bookmarks; search across everything; edit, retag or export. When you're done you can restore the file (or an edited copy) back into JW Library.
What's actually inside the file
Technically a .jwlibrary file is a zipped SQLite database plus a manifest. That's why renaming it to .zip sometimes happens by accident in transit — and why renaming it back to .jwlibrary fixes it. You never need to know any of that to use it, but it explains why the file is small, self-contained and identical across Android, iPhone, iPad and Windows.
Opening it on a computer
The same jwsync.org page works on a laptop or desktop browser — handy for reading years of notes on a big screen, or doing bulk clean-up that would be tedious on a phone. There's nothing to install.
What the file actually is
A .jwlibrary file is a ZIP archive with a different extension. Inside it are userData.db — a SQLite database holding your notes, highlights, bookmarks and tags — and manifest.json, a small file describing the backup, including a hash of the database that JW Library uses to confirm the file has not been altered. Nothing about it is proprietary or encrypted; it is a standard archive around a standard database.
Opening it without JW Library
You do not need the app, or any software, to read your own backup. Opening the file in your browser shows every note, highlight and bookmark it contains, with search and filtering, and the file never leaves your device — it is read locally rather than uploaded. This is the fastest way to confirm a backup contains what you think it does before a reset, a trade-in, or a restore onto a new phone.
Looking inside manually
If you are curious, copy the file, rename the copy to .zip and open it with any archive tool. You will see userData.db and manifest.json. Opening the database needs a SQLite viewer, and the tables are named for what they hold — Note, UserMark, Bookmark, Tag. Always work on a copy: editing the database by hand without updating the manifest hash produces a file JW Library will refuse to restore.
Editing safely
Notes can be corrected, retagged, recoloured or deleted outside the app, and the result exported as a new .jwlibrary file you restore normally. The rule that keeps this safe is to keep the original: edit a copy, restore the edited file, and if anything is not as you expected, the untouched original is still there to fall back on.
Reading a backup on a phone
You do not need a computer. Opening the file in a mobile browser works the same way, which is useful when the backup is already on the phone and you want to confirm its contents before restoring or before wiping the device. The file is read locally, so this works with no connection beyond loading the page itself.
Why the manifest hash matters
manifest.json records a hash of userData.db. JW Library uses it to confirm the database has not been altered since the backup was written, so a file whose database has been edited without the hash being recalculated is refused on restore. This is the single most common reason a hand-edited backup stops working, and the reason editing through a tool that rewrites the manifest is safer than editing the database directly.
What this is good for
Being able to read a backup changes what a backup is worth. You can confirm a file contains what you think before wiping a phone, check whether an old file is worth restoring, find a note you know you wrote without hunting through the app, or recover text from a file JW Library will not accept. None of it requires trusting the file to anyone — it is read on your own device.
Frequently asked questions
- Can I open a .jwlibrary file in Excel or Notepad?
- Not usefully — it's a database, not a spreadsheet or text file. Open it in JW Sync to read it, or export your notes to Markdown/text from Study Explorer.
- Is it safe to open my backup in the browser?
- Yes. JW Sync reads the file locally in your browser tab; nothing is sent to a server, and your original file is never modified.
- Can I just rename it to .zip?
- Yes, on a copy. Renaming does not alter the contents, and it lets any archive tool show you what is inside.
- Will opening the file change it?
- No. Reading a backup — in the browser or an archive tool — leaves it byte-for-byte unchanged. Only saving or exporting produces a new file.
- Do I need to be online?
- Only to load the page. The file itself is read on your device, not uploaded, so your notes never travel over the network.
- Can I open a backup someone else sent me?
- Yes, the format is not tied to a device or account. Whether you should restore it is a separate question, since restoring replaces your own library.
- Do I need to install anything to look inside?
- No. A browser is enough to read the notes; only manual inspection of the database itself needs a SQLite viewer.