Can I download a Facebook story?

The 24-hour clock changes what the question is

A Facebook story is up for a day. After that it is off the story tray for everyone who was not the person who posted it, and the address it lived at stops serving anything. That single fact reshapes the whole problem.

With a feed video or a reel you can be leisurely. The post sits there, you find it again next week, you save it then. A story gives you one window, and by the time most people go looking for a way to save one the window is already closing. So the honest first instruction on this page is not about apps at all: if you want a story, deal with it now. Nothing recovers an expired story — not a downloader, not a cache, not a service claiming to have one.

The second thing the clock does is set expectations about what a story even is. It is a deliberately temporary post shown to a chosen audience. Facebook builds the whole feature around that promise, and the technical arrangements underneath it follow from the promise. Which is why the rest of this page reads less like a how-to and more like a map of where the line sits.

Why most story links do not resolve

A story URL looks like facebook.com/stories/<id>/ and it goes into Savvy's link field without complaint. That is not the same as it working, and the distinction is where most of the confusion on this subject lives.

Savvy identifies a link by its host. Anything on facebook.com — including the mobile and legacy hosts, and the fb.watch and fb.me short links — is recognised as Facebook and accepted. Whether there is anything to fetch at the other end is a completely separate question, answered not by the app but by Facebook, when the extraction chain requests that page.

And for a story, Facebook's answer is usually no. A downloader makes an ordinary, signed-out request. Stories are served to a signed-in account that the poster has included in the audience. Present none of that and Facebook returns a login wall rather than a video, which the chain reports back as a failure. The Facebook specialist in Savvy's provider chain is unambiguous about it: hand it restricted content and it redirects to an error rather than producing a file.

There is no Facebook sign-in inside Savvy that would change this. Instagram is the one platform where the app holds a session of your own — a separate in-app login on its own screen, used only by the Instagram stories feature. Facebook has no equivalent, by design.

So the practical test is a five-second one, and it is worth doing before you assume something is broken:

• Open the story link in a private or incognito browser window, where you are not signed in to Facebook
• It plays — a downloader can fetch it too
• It shows a login wall — no downloader will do better, whatever its listing promises
• It says the story is unavailable — the 24 hours are up, and nothing brings it back

If a story link does open signed-out

When the signed-out test passes, the rest is ordinary and quick.

The fast route is the share sheet. Open the story, tap the share control, scroll Facebook's own options to Share to other apps, and pick Savvy. The link is handed across and the download starts on its own — you never see Savvy's home screen and you type nothing.

The slower route is copy-and-paste: take Copy link, open Savvy, tap the Paste button beside the link field, then tap Download. Paste is exactly what it sounds like and no more. Savvy does not watch your clipboard in the background, and switching to the app starts nothing; Paste reads the clipboard once when you tap it and fills the field, and Download is a separate deliberate tap.

Stories are vertical, which turns out to matter for what they cost. Savvy prices a video on its shorter side, so a full-height 1080-by-1920 story is counted as 1080 and sits in the ordinary HD band rather than anything dearer, and a smaller one at 480 across is counted as 480 — which is free, out of a daily allowance rather than any balance. Stories are, in cost terms, among the cheapest things to save. Coins above that ceiling are earned by watching a short rewarded ad or checking in daily, or bought in packs; the free tier is ad-supported through Unity Ads, which collects your device's advertising ID, as the Savvy privacy policy sets out.

• SD video, up to 480 on the short side — free, from your daily allowance
• HD and Full HD — 10 coins, or one HD credit; a 1080x1920 story lands here
• 2K — 15 coins, 4K — 20 coins
• A photo story — 5 coins, the flat image rate

Keeping your own story

Your own story is the case where you unambiguously hold every right that matters, and it is also the case a downloader is least suited to — because the obstacle is a login wall, and it is your login. The tool for the job is Facebook's own.

While the story is live, open it and use the menu on the story itself; Facebook offers a save option there, though the exact wording and its position move around between app versions. If you have story archive switched on, Facebook keeps your expired stories privately for you and you can save them from there afterwards — which is by some distance the most reliable way to keep your own, because it survives the 24 hours that everything else on this page does not.

Worth turning archive on before you need it rather than after. It is the difference between a story being recoverable and being gone, and the setting is doing nothing until the day it is doing everything.

One thing not to bother with: pushing your own story's link into a downloader. The link is not publicly resolvable — that is exactly the point of a story — and the fact that it is yours makes no difference to a signed-out request. It is not a permissions problem the app can be talked around; the page simply is not being served.

Someone else's story, and where the line sits

The question people arrive with is usually about someone else's story, so it deserves a straight answer rather than a hedge.

If you can see a story, you can screen-record it — every modern phone has that built in, it needs no app, and it works regardless of what Facebook serves to a signed-out request. Nobody sensible will pretend otherwise. What it produces is a lower-quality copy with your notification bar in the frame, and it is the reason the question is rarely really a technical one.

The real question is what you then do with it. Keeping a friend's story because it is a photo of you, or because they asked you to, is one thing. Saving someone's story so you can re-share it somewhere they did not choose to post it is another, and it defeats the entire reason they used a format that expires. Facebook does not notify anyone about screen recording on stories, which means the restraint has to come from you.

There is also a plain legal layer beneath the etiquette. A story is its author's work, and downloading it confers no rights over it. Personal viewing sits in very different territory from reposting or monetising, and that distinction does not care which method produced the file. Is downloading videos legal? sets out where the line usually falls between keeping something and using it.

Where saved files land, and what Savvy is better at

When a story does resolve, the file goes to your device's Downloads folder, in a Savvy directory, in a subfolder named for the platform — Downloads / Savvy / Facebook. It is an ordinary file from there: it appears in your gallery and plays or opens in anything. Inside the app, Library lists everything you have saved with search and filters, and Storage shows what each file is taking up.

It is worth being honest about where this app is strongest, since you may have come here for stories generally rather than Facebook's specifically. Savvy has a dedicated Stories screen, and it covers two things well: WhatsApp status, which is read straight off your own device with no link and no login, and Instagram stories, which work through a separate in-app Instagram login of your own. Both are proper first-class flows.

Facebook stories are not one of them. They go through the ordinary link field, they succeed only when the story is publicly reachable, and for personal stories that is rarely the case. That is a smaller promise than the search term implies, and it is the true one.