What "Cloud" Means When It's Your Manuscript

Ask three people what "the cloud" means and you'll get three shrugs and one confident wrong answer. For most files, that vagueness costs nothing. For a manuscript, it's worth ten straightforward minutes, because the word is doing a lot of hiding.

What "cloud" actually describes

The cloud is a computer that belongs to someone else. When a writing app calls itself cloud-based, your pages are usually stored on a server the company operates, and the app on your phone or laptop is a window onto that server rather than the place where the file itself lives. Some apps also keep a full copy on your own device, quietly, in the background, so you're covered either way. Plenty don't. Close the laptop lid with no connection and there's nothing on the machine but a login screen waiting for one.

Cloud backup and cloud-only storage are not the same thing

These two get sold with the same word, and they behave very differently. A cloud backup means your working file lives on your device first, and a copy travels to a server as insurance, the way a spare key lives at a neighbor's house. Cloud-only storage means the server copy is the only real one, and your device just borrows a view of it while you're connected. Both are reasonable designs. The difference is which copy is the one that survives if a company disappears, a subscription lapses, or a server has a bad day. Worth knowing which one you're actually using, since the marketing page rarely says it plainly.

Why the label alone won't tell you which one you have

"Cloud-based" got adopted as a selling point somewhere along the way, standing in for reliability in general, regardless of which architecture sits underneath it. That's a shortcut, not a lie exactly, but it means the word on a pricing page tells you almost nothing about which of the two designs above you're getting. The only way to know is to look past the label: read the help pages, search the app's own name plus "offline," or run the five-minute test further down this page. A manuscript is worth that extra ten minutes in a way a shopping list isn't.

Where your pages live when you're not looking

This matters in three ordinary moments. On a train, a bus, or anywhere the connection drops mid-sentence: does the app keep writing normally, or does it stall, grey out, or refuse to open at all? Months from now, if a company changes its pricing or closes down: is there a copy of your novel already sitting on your own machine, in a format something else can open, or does every paragraph you've written live exclusively on a server tied to an account you might not keep forever? And right now, today: who else, technically, can open that file? Usually nobody but you. Support staff can sometimes see it if you ask for help with a problem, which is ordinary and disclosed in most privacy pages, but it's worth knowing the door exists rather than assuming it doesn't.

What "offline" really means

Two apps can both claim to work offline and mean different things by it. One keeps a genuine local copy: you can write for a week with no connection at all, and every word sits on your disk the whole time, no different from a plain document. The other keeps a temporary holding area: it lets you type for a while, but your edits wait there until the connection returns, and a crash or a badly timed update can lose whatever was waiting. This is the same distinction that separates an app that happens to talk to a server sometimes from a tool that has no meaningful existence without a browser tab and a live connection. The difference rarely shows up in the marketing. It shows up in the help pages, described more carefully, or in a forum thread where someone already asked and got a real answer.

A five-minute test

Turn off your connection, write a paragraph, and watch what happens. Then look in your own file manager, not the app's internal file list, for something you can find without logging in anywhere. If nothing turns up, that's useful information rather than a failure on your part. It tells you, plainly, where your manuscript actually is when the app itself isn't running.

Four checks before you trust it with a manuscript

Is there a plain file on your device that exists without you being logged in?
What happens the instant your connection drops mid-sentence?
If you exported everything today, what format would you get, and could something else open it?
If you stopped paying tomorrow, could you still read what you already wrote?

None of these questions require an answer you like. They just require an answer you actually know, for the one file that took years to write. A manuscript is a strange kind of document: too big to hold in memory, too personal to leave to a guess about where it lives, and too easy to assume is safer than it is simply because the word "cloud" sounds like weather rather than a hard drive somewhere with a company's name on the lease.

How Scrin does it

Your project stays in a file you own. Every change is restorable from version history, and a plain-text copy is written next to it every day.

Try Scrin early — leave your email and we'll open the web version to you.