Publié
Margina vs. Apple Books: Sending Files vs. Buying From a Store
Apple Books does two things at once: it sells you books through its store, and it lets you import files you already have — a PDF, an EPUB, a chapter someone emailed you. The two paths don't behave the same way once you're inside the app. Purchased books sync differently than imported ones, some formats won't open at all, and PDFs don't get the same reading experience as a bought title. Here's what actually changes, and where a file-first app fits.
The thought
Apple Books does two things at once, and it's easy to lose track of which one you're doing. You can buy a book from its store, the way you'd buy anything from Apple — one tap, one download, tied to your Apple Account forever. Or you can send yourself a file you already own: a PDF contract, an EPUB you downloaded from a library site, a chapter a friend emailed you. Both end up on the same shelf, in the same app. They don't behave the same way once they're there.
That difference matters more than it looks. A store is built to sell you things and keep track of what you bought. A file-import feature is bolted onto that store, and it shows. Once you notice where the seams are — what syncs, what opens where, what won't come in at all — the choice between owning your books as files, not apps and owning them as store purchases starts to look like two different products wearing one interface.
The longer version
Buying from the store
Buying is the easy path, because Apple designed it that way. You pay, the book attaches to your Apple Account, and it shows up in your library. But "shows up" doesn't mean "syncs everywhere automatically." Apple is specific about this in its own documentation: purchased content isn't pushed to every device the moment you buy it. On a new iPhone, iPad, or Mac, you have to download books you purchased on other devices before you can actually read them there. Manageable, but a step — and an easy one to forget about until you're standing in an airport with no signal and a book you paid for that isn't on the device in your hand.
Sending a file you already own
Importing works differently, and it starts outside the store entirely. On a Mac, you open Books, choose File > Import, and select the files — or drag and drop them straight into the library. Apple supports EPUB books, PDFs, and some MP3 and Audible audiobooks this way. Genuinely useful. It's also where the seams start to show.
First seam: imported PDFs don't get the same reading experience as a bought book. Apple's guide says it plainly — PDFs "open in Preview (or your default PDF reader), rather than in Books." A PDF you send yourself ends up in your library as little more than a shortcut to another app, not a document Books actually renders.
There's a second seam, and it's more absolute. Some formats can't come in at all. Files with certain copy protection — Apple names ACSM, AZW, and ODM specifically — "can only be opened in the associated third-party app." Own a document in one of those formats and importing simply isn't on the table; you're routed elsewhere.
A third seam is quieter. Apple's iCloud documentation walks through exactly how purchased books sync across devices, and says nothing about imported files doing the same. That's not proof they don't sync — it just means the one place you'd look for an answer doesn't give you one.
What a file-first app changes
None of this makes Apple Books a bad idea. It makes it two features sharing one shelf, and the newer of the two — importing — inherits none of the polish built for the older one. A file-first app skips that tension by never having a separate "buy" path to reconcile with an "import" path in the first place. Every document in Margina got there because you sent it, so there's nothing to reconcile — no purchased shelf behaving one way and an imported shelf behaving another, no PDF quietly redirected somewhere else. The library stores locally, backs up to iCloud or Drive on your terms, and doesn't ask for an account to do any of it. The free tier covers a working number of documents before you'd consider paying for more.
A useful corollary
This isn't really an Apple Books problem. It's what happens whenever a tool is built around a catalog and then grows a way to hold things that aren't in the catalog. Read-it-later apps do this too — bookmark a page and it behaves like a citizen of the app right up until it doesn't. DRM-locked formats do it in the other direction: a file that looks like yours but only opens where its publisher allows.
The comparison holds for Kindle, too — a marketplace-first app handling personal files is a different problem than a files-first app handling personal files, even when the end result looks similar on a shelf. It's also why a small category of specialist readers exists at all. A roundup of iPad and iPhone ebook readers notes that apps like BlueFire Reader and Serial Reader are built specifically to "add your EPUB and PDF files," while marketplace apps like Kindle or Kobo lean toward buying first and treating import as an afterthought. Neither approach is wrong. They're just answering different questions.
So the real question isn't which app has the better store, or the better import button. It's simpler than that: is most of what you read something you bought, or something you already have? If it's mostly the second, an app built around files — rather than one built around a catalog with files added later — starts to feel less like a workaround and more like the actual shape of your library.