Facebook Page Reels Scraper – Video Feed Export

Collect public Reels from known Facebook Pages without finding every video link first. Facebook Page Reels Scraper exports Reel captions, publication times, engagement, video references, audio and author details, with the source Page in each row.

Set a page limit for each input to build a public video inventory or compare recent short-form content across Pages. Each Reel stays in one table row with matching flat JSON fields. No Facebook login or cookies are required.

At a glance	Details
📥 Input	Page usernames, numeric IDs as strings, or Page URLs
📤 Output	Public Reel captions, metrics, video and audio details, author and source Page
🔐 Login required	No Facebook credentials or cookies
📄 Collection	Pagination; pagesPerProfile defaults to 1
💾 Delivery	One row per distinct Reel returned for each source Page; JSON, CSV, Excel or API

What the Facebook Page Reels Scraper extracts 🔎

The Actor reads the Page’s public Reels section and collects available metadata for each distinct returned Reel.

• Reel, post and story IDs, canonical URL, caption text and publication time
• Play, reaction, comment and share counts when exposed
• Thumbnail, available HD and SD video URLs, duration and dimensions
• Available caption-file and streaming-manifest fields
• Author identity, audio metadata, sponsorship, reshare and remix flags
• Reaction breakdown and source Page information

How to scrape Facebook Page Reels 🚀

1. Add the usernames or URLs of Pages whose public Reels sections you want to collect.
2. Set pagesPerProfile; start with 1 to inspect the available collection.
3. Start the Actor and inspect the dataset’s status column.
4. Export successful rows or connect the results to your workflow.

{
  "inputList": [
    "Meta"
  ],
  "pagesPerProfile": 1
}

Facebook Page Reels data fields and output 📦

Field group	Included data
Reel identity	IDs, URL, type, caption, timestamp and publication date
Engagement	Plays, reactions, comments, shares and aligned reaction lists
Video	Thumbnail, HD/SD URLs, duration, dimensions, captions and streaming fields
Author and audio	author.* profile details and audio.* metadata
Flags	Sponsorship, resharing and remix status
Source Page	source_profile.* identity, URL, image and verification

Complete representative success item. All names, counts and media addresses below are illustrative, not a live result; every current output field is included.

{
  "input": "HarborCoffee",
  "status": "success",
  "id": "1234567890123456",
  "post_id": "122345678901234567",
  "story_id": "UzpfSTEwNDU2Nzg5MDEyMzQ1NjoxMjIzNDU2Nzg5MDEyMzQ1Njc=",
  "url": "https://www.facebook.com/reel/1234567890123456/",
  "type": "reel",
  "message": "A look at our morning espresso routine.",
  "timestamp": 1785574800,
  "published_at": "2026-08-01T09:00:00Z",
  "play_count": 12500,
  "reactions_count": 340,
  "comments_count": 18,
  "shares_count": 27,
  "thumbnail_url": "https://media.example.com/espresso-reel.jpg",
  "video_url_hd": "https://media.example.com/espresso-reel-hd.mp4",
  "video_url_sd": "https://media.example.com/espresso-reel-sd.mp4",
  "duration_ms": 18000,
  "width": 1080,
  "height": 1920,
  "captions_url": "https://media.example.com/espresso-captions.vtt",
  "dash_manifest": "",
  "is_sponsored": false,
  "is_reshare": false,
  "remix_status": "DISABLED",
  "author.id": "100091234567890",
  "author.page_id": "104567890123456",
  "author.username": "HarborCoffee",
  "author.name": "Harbor Coffee",
  "author.url": "https://www.facebook.com/HarborCoffee/",
  "author.profile_picture_url": "https://media.example.com/harbor-coffee-profile.jpg",
  "author.is_verified": false,
  "audio.id": "765432109876543",
  "audio.type": "original",
  "audio.title": "Original audio · Harbor Coffee",
  "audio.cover_url": "https://media.example.com/harbor-coffee-audio.jpg",
  "audio.is_original_audio": true,
  "reactions.id": [
    "1635855486666999",
    "1678524932434102"
  ],
  "reactions.type": [
    "LIKE",
    "LOVE"
  ],
  "reactions.count": [
    280,
    60
  ],
  "video.id": "1234567890123456",
  "video.type": "video",
  "video.url": "https://www.facebook.com/reel/1234567890123456/",
  "video.image_url": "https://media.example.com/espresso-reel.jpg",
  "video.thumbnail_url": "https://media.example.com/espresso-reel.jpg",
  "video.video_url_hd": "https://media.example.com/espresso-reel-hd.mp4",
  "video.video_url_sd": "https://media.example.com/espresso-reel-sd.mp4",
  "video.dash_manifest_url": "",
  "video.dash_manifest": "",
  "video.duration_ms": 18000,
  "video.width": 1080,
  "video.height": 1920,
  "video.alt_text": "A barista preparing an espresso.",
  "video.captions_url": "https://media.example.com/espresso-captions.vtt",
  "source_profile.id": "100091234567890",
  "source_profile.page_id": "104567890123456",
  "source_profile.username": "HarborCoffee",
  "source_profile.name": "Harbor Coffee",
  "source_profile.url": "https://www.facebook.com/HarborCoffee/",
  "source_profile.profile_picture_url": "https://media.example.com/harbor-coffee-profile.jpg",
  "source_profile.is_verified": false
}

The table and JSON use the same flat keys and values, with one row per result. Dots in keys such as source_profile.name are literal parts of the field name.

Reaction IDs, types and counts occupy aligned lists: matching positions describe the same reaction. source_profile.* identifies the requested Page, while author.* identifies the author supplied with the Reel.

Successful rows may contain empty strings, zeroes, false flags, empty lists or nulls when optional information is unavailable. Do not interpret a default count or flag as a confirmed source fact. Failed rows retain input, set status to failed, and use null result fields.

Input requirements and coverage ⚙️

Parameter	Type	Required	Rules
inputList	array of strings	Yes	At least one Page username, numeric ID as a string, or supported Page URL; no default target.
pagesPerProfile	integer	No	Default 1; minimum 1, maximum 100. Maximum result pages to attempt per input.

Use Page usernames, numeric IDs as strings, standard Page URLs, profile.php?id=... links or legacy /pages/NAME/ID links. Individual Reel URLs belong in Facebook Reel Details Scraper. This actor collects the Reels section, not a mixed post feed.

The initial results count as page 1. Further pages are requested only while Facebook supplies a usable continuation. Page size is controlled by the source, so this is not an exact record limit.

Provide an array of strings, not URL objects. An invalid overall input structure stops processing without dataset rows; an invalid target within a valid list is recorded as a failed result. The input schema does not set a maximum list length; choose batch sizes appropriate to your run limits.

Facebook Page Reels use cases 🎯

Short-form content reporting

Compare public captions, publication times and available engagement figures across selected Page Reel collections.

Video asset inventories

Keep Reel IDs, video references, thumbnails, duration and dimensions together for authorized review or cataloging.

Page content monitoring

Schedule small recurring exports to track newly visible Reels and changes in public engagement counts.

Pricing and billable Reel rows 💰

Check the Actor’s Pricing tab for the current model and rate. That configuration is authoritative.

Under dataset-item pricing, saved success and failed rows can count toward charges. Each distinct returned Reel saves a success row. Invalid inputs, an empty first collection or a persistently unavailable result page can save failed rows; a later failure does not remove earlier results. Retries do not independently add dataset rows. All details remain in their result row.

Facebook Page Reels Scraper API and integrations 🔌

Replace $ACTOR_ID with the ID shown in the Actor’s API tab and $APIFY_TOKEN with your Apify token.

curl -X POST "https://api.apify.com/v2/acts/$ACTOR_ID/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"inputList":["Meta"],"pagesPerProfile":1}'

Start runs through the Apify API, schedules or client libraries. Use webhooks for completion events and export the dataset to spreadsheets, Make, Zapier, storage or your own application.

Reliability and limits ⚠️

Results depend on the Reels Facebook exposes publicly. Some Pages provide fewer items or fewer metadata fields than others, and continuation may end before the requested page limit. Repeated Reel IDs are skipped within the same Page crawl.

Video and caption URLs are references supplied by Facebook and can expire or require renewed access. The Actor does not download or store video files. Temporary request failures are retried, and a page that remains unavailable can create a failed row.

Frequently asked questions ❓

Does this also return regular Page posts?

No. It collects the public Reels section. Use the appropriate content actor for other Facebook surfaces.

Can I provide a single Reel link?

Use Facebook Reel Details Scraper for known /reel/ URLs. This actor starts from the Page.

Are the video files downloaded?

No. Results contain available media URLs and metadata. Those URLs may expire.

Does it include comment text?

No. comments_count is a count. Use Facebook Post Comments Scraper to request visible comments for a selected Reel.

Will a larger page limit collect every Reel?

Not necessarily. Public visibility and the continuation Facebook provides determine what can be reached.

Support, responsible use, and related actors 🛟

For help with missing or unexpected results, open an Issue on this Actor’s Apify page with the run link, a public example input and the fields you expected. Keep tokens and credentials out of support messages.

Use public data only for purposes you are authorized to pursue, respecting privacy, platform terms and content rights.