Capture Instagram and Facebook stories
Collect live stories and Instagram highlights in the Page Vault Browser and send them straight to Batch.
The Page Vault Browser can capture Instagram stories, Instagram highlights, and Facebook stories in one step. Open the profile or Page, start the capture, and the browser collects the stories and sends them to Batch for you.
You no longer need to copy media links from a third-party site or from developer tools and paste them into a Batch job by hand: Watch the demo video
Before you start:
- Story capture works in the Page Vault Browser and is available on every account that uses it.
- You need to be signed in to Instagram or Facebook inside the Page Vault Browser.
- Stories are viewed as the account you're signed in with. If a profile is private, you'll only see its stories if that account has access to them.
- Stories disappear after 24 hours, so capture them as soon as you can.
Capture Instagram stories and highlights
- Sign in to Instagram in the Page Vault Browser.
- Open the profile you want to capture.
- Click Get stories.
The browser collects the account's live stories and highlights and sends them to Batch right away. Here's what you'll get:
- Videos go to a Videos job.
- Photos go to a Documents job.
- A PDF of the story viewer page, which shows the account's username and how long ago the story was posted.
Capture Facebook stories:
- Log in to Facebook in the Page Vault Browser. If you aren't logged in, the capture stops and asks you to log in.
- Open the Facebook Page or profile you want to capture.
- Choose the Facebook stories capture type. You'll find it next to the page capture option.
- If you also want a PDF of each story card, turn on Capture each story page. This option is off by default.
Here's what you'll get:
- Every card in the live story goes to one Documents job, named after the Page owner.
- If you turned on Capture each story page, you also get a PDF of each story card's viewer page.
Facebook Pages don't have highlights, so Facebook capture covers live stories only.
Jobs are sent right away. Story media links expire within a few hours, so the browser sends your jobs to Batch as soon as it collects them. If a photo fails and you retry it much later, the retry may fail because the link has expired. If that happens, go back to the profile and capture the stories again while they're still live.
Some Facebook story cards are skipped. A few Facebook story cards don't contain any media. The browser skips these, so your job may have fewer items than the number of cards you saw.
Troubleshooting:
-
I see "This Page has no live stories right now." The Facebook Page doesn't have any active stories at the moment. Stories only stay up for 24 hours, so there may be nothing to capture yet. Check back later.
-
The Facebook capture stopped and asked me to log in. You need to be logged in to Facebook in the Page Vault Browser. Log in, open the Page again, and choose Facebook stories.
-
I can't see a private profile's stories. The browser views stories as your signed-in account. If that account doesn't follow the private profile or can't see its stories, the browser can't capture them either.
-
A photo failed when I retried it. Story media links expire within hours. Capture the stories again from the profile while they're still live.
-
My Facebook job has fewer items than I expected. Story cards without media are skipped. Everything else in the live story is included.
Frequently Asked Questions:
-
Do I still need to copy story links from a third-party site? No. The Page Vault Browser now collects the stories for you and sends them to Batch.
-
Can I capture Instagram highlights? Yes. Get stories captures both live stories and highlights on an Instagram profile.
-
Can I capture Facebook highlights? No. Facebook Pages don't have highlights, so Facebook capture covers live stories only.
-
Where do my captures go? They're sent to Batch automatically. On Instagram, videos go to a Videos job and photos go to a Documents job. On Facebook, all story cards go to a single Documents job named after the Page owner.