Facebook Reels Scraper

Facebook Reels Scraper

Facebook Reels Scraper is a fast, reliable Facebook Reels scraper tool that helps you scrape Facebook Reels data from public profiles at scale. It collects captions, publish time, views (play counts), and rich media metadata into your Apify dataset — ideal for marketers, developers, data analysts, and researchers. Use it as a Facebook Reels metadata extractor for competitive analysis, content libraries, and Facebook Reels scraping automation.

What is Facebook Reels Scraper?

Facebook Reels Scraper is a production-ready Apify actor that discovers public Reels on the profiles you provide, then fetches each Reel’s page to extract structured metadata and media details. It solves the manual, error-prone process of mining Reels content by streaming clean, structured records to your dataset as each Reel is saved. Built for teams that need a bulk Facebook Reels scraper or a Facebook Reels scraper API/Python integration, it enables ongoing monitoring and large-scale automation.

What data / output can you get?

Below are real output fields this Facebook Reels data extractor saves to the Apify dataset for each Reel (fields may be empty when not available):

Data field	Description	Example value
startUrl	The profile URL you provided for discovery	https://www.facebook.com/LeonardoDiCaprio/
facebookUrl	Resolved base profile/page URL from the Reel owner	https://www.facebook.com/LeonardoDiCaprio/
inputUrl	The exact Reel page URL that was fetched	https://www.facebook.com/reel/1234567890123456
topLevelUrl	Post-level URL derived from page JSON (when present)	https://facebook.com/1234567890123456/posts/undefined/
topLevelReelUrl	Canonical sharable Reel URL	https://www.facebook.com/reel/1234567890123456/
text	Reel caption/description text	Protecting our planet starts today…
time	ISO UTC timestamp of publish time (when resolvable)	2026-03-01T12:34:56.000Z
play_count_reduced	Human-readable play count string	3.6M
playCountRounded	Parsed numeric play count	3600000
shareable_url	Shareable URL from the Reel context	https://www.facebook.com/reel/1234567890123456
video_owner_type	Owner type (from context)	FACEBOOK_USER
video_owner	Owner object with id, name, url, etc.	{"name":"Example Page","url":"https://www.facebook.com/example"}
playback_video	Player metadata (thumb, image.uri, permalink_url, audio language, etc.)	{ "permalink_url": "https://…", "image": {"uri": "https://…"} }
video	Video metadata merged from the page (duration, thumbnail, embeddable flag)	{ "__typename": "Video", "playable_duration_in_ms": 15000 }
attachments	Raw attachments array when available	[]
tracking	Tracking context object (may include top_level_post_id)	{"top_level_post_id":"1234567890123456"}
is_passive_content	Passive content flag	false
fb_shorts_reshare_context	Reshare info	{}
remix_info	Remixability info	{}
soundtrack_info	Audio metadata when available	{"type":"CUSTOM_AUDIO"}
track_title	Audio label when available or synthesized	Example Page · Original audio
music_album_art_uri	Album art URL when available	https://…
if_should_change_url_for_reels	URL-change hint with shareable_url	{"shareable_url":"https://www.facebook.com/reel/123…"}

Error/info fields that may appear:

• request_error: Set when the Reel request fails (e.g., RequestException class name).
• parse_error: Set when the page JSON didn’t include expected nodes.
• http_status: Non-200 status returned by the Reel page request.
• error and type: On profile-level failures, a row is pushed like {"startUrl": "...", "error": "message", "type": "profile_error"}.

Notes:

• Data streams to the dataset as each Reel is processed. Export in JSON, CSV, or Excel from the Apify dataset UI.
• Direct media URLs may appear under playback_video.videoDeliveryLegacyFields when available.

Key features

• 🚀 Fast, parallel collection Collect and parse many Reel pages per profile with tuned concurrency and backoff for reliability at scale.

• 🎯 Precise metadata extraction A focused Facebook Reels metadata extractor that pulls captions, publish timestamps, play counts, owner info, and media fields cleanly from public pages.

• 📦 Streaming to dataset Records are pushed as soon as each Reel is processed — no need to wait for the whole run to finish.

• 🧭 Pagination-aware discovery Smart profile scanning with GraphQL pagination when possible, honoring your Max Reels per profile limit for bulk Facebook Reels scraper workflows.

• 🔒 Proxy support for stability First-class Apify Proxy integration (RESIDENTIAL recommended) to reduce blocking and improve consistency.

• 💻 Developer-friendly Run via Apify API, build a Facebook Reels scraper Python workflow, or plug into orchestration tools for Facebook Reels scraping automation.

• 🔗 Integration-ready exports Export to JSON, CSV, or Excel and connect datasets to downstream BI pipelines, CRMs, or automation (Zapier/Make/n8n) with the Apify ecosystem.

• 🧱 Production-grade resilience Built-in retries, adaptive backoff, and graceful error reporting (request_error, parse_error, http_status) for reliable, unattended runs.

How to use Facebook Reels Scraper - step by step

1. Create your Apify account Sign up or log in at apify.com.

2. Open the actor Find “Facebook Reels Scraper” in the Apify Store and click Try for free.

3. Add profile targets In “Profile URLs” (startUrls), paste one or more profile/page URLs or usernames (e.g., https://www.facebook.com/LeonardoDiCaprio/ or just LeonardoDiCaprio).

4. Set limits Use “Max Reels per profile” (resultsLimit) to cap how many Reels you collect per profile (1–10,000).

5. (Optional) Filter by time Enter “Only posts newer than” (onlyPostsNewerThan) as a date (YYYY-MM-DD) or a relative window like “7 days” to skip older Reels.

6. Configure proxy Use Apify Proxy with RESIDENTIAL group in proxyConfiguration for smooth, consistent collection.

7. Run the scraper Click Start. The actor discovers Reel IDs and fetches each Reel page. Rows appear in the run’s Dataset as they’re saved.

8. Download results Open the Dataset tab and export your data to JSON, CSV, or Excel for analysis or automation.

Pro Tip: Schedule runs and access results via the Apify API to build an automated Facebook Reels scraper API pipeline or integrate with your Facebook Reels scraper Python scripts.

Use cases

Use case	Description
Marketing + trend tracking	Monitor public Reels from key creators to spot content themes and best-performing formats using structured metadata and play counts.
Competitive analysis	Compare posting cadence, topics, and play volume across competitor profiles for strategic benchmarking.
Content library building	Archive captions, timestamps, and media metadata to power ideation, repurposing, and editorial calendars.
Reporting & analytics	Export to CSV/JSON/Excel and feed dashboards for weekly or monthly performance summaries.
Developer pipelines (API/Python)	Trigger runs via API and pipe dataset exports into ETL jobs for end-to-end Facebook Reels scraping automation.
Academic & research	Collect longitudinal, public Reels metadata for studies on engagement patterns, topics, or media usage.
Bulk projects	Use resultsLimit (up to 10,000 per profile) to scale discovery and collection for large datasets.

Why choose Facebook Reels Scraper?

A precise, automated, and reliable Facebook Reels data extractor built for scale and repeatability.

• ✅ Accuracy you can trust: Extracts only structured metadata directly from public Reel pages with robust parsing.
• 🌍 No login required: Works on public content without cookies or accounts; use Residential proxy for best stability.
• 📈 Built for scale: Handles multi-profile, high-volume runs with streaming dataset output and robust backoff.
• 💻 Developer access: Integrate via Apify API or connect with your Facebook Reels scraper Python workflows.
• 🔗 Easy integrations: Export JSON/CSV/Excel and hook into automation tools and BI stacks.
• 🛡️ Safer than extensions: Runs in the cloud with consistent headers and proxy controls — no brittle browser plugins.
• 💰 Cost-effective automation: Run repeatably on schedules to cut manual effort and consolidate data reliably.

In short: a production-ready alternative to fragile, ad hoc methods — optimized for automation and data quality.

Is it legal / ethical to use Facebook Reels Scraper?

Yes — when used responsibly. This actor targets publicly available Facebook Reels content and does not access private or authenticated data.

Guidelines for compliant use:

• Only collect public profile Reels.
• Avoid personal/sensitive data and respect platform terms.
• Comply with data protection laws (e.g., GDPR/CCPA) as applicable to your use case.
• Use proxies responsibly and pace your runs.
• When in doubt, consult your legal team for edge cases.

Input parameters & output format

Example input

{
  "startUrls": [
    "https://www.facebook.com/LeonardoDiCaprio/",
    "mrbeast"
  ],
  "resultsLimit": 20,
  "onlyPostsNewerThan": "7 days",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}

Input fields

• startUrls (array of string) — One or more Facebook profile/page URLs or usernames. Required: Yes. Default: none.
• resultsLimit (integer) — Max Reels to collect per profile (newest-first where available). Required: No. Default: 10. Min: 1, Max: 10000.
• onlyPostsNewerThan (string) — Date/time filter. Accepts absolute date (YYYY-MM-DD) or relative window like “7 days”. Required: No. Default: "" (no cutoff).
• proxyConfiguration (object) — Route traffic via Apify Proxy. Residential proxy recommended. Required: No. Default prefill: {"useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"]}.

Example output

{
  "startUrl": "https://www.facebook.com/LeonardoDiCaprio/",
  "facebookUrl": "https://www.facebook.com/LeonardoDiCaprio/",
  "inputUrl": "https://www.facebook.com/reel/1234567890123456",
  "topLevelUrl": "https://facebook.com/1234567890123456/posts/undefined/",
  "topLevelReelUrl": "https://www.facebook.com/reel/1234567890123456/",
  "text": "Protecting our planet starts today…",
  "time": "2026-03-01T12:34:56.000Z",
  "play_count_reduced": "3.6M",
  "playCountRounded": 3600000,
  "shareable_url": "https://www.facebook.com/reel/1234567890123456",
  "video_owner_type": "FACEBOOK_USER",
  "video_owner": {
    "name": "Example Page",
    "url": "https://www.facebook.com/example"
  },
  "playback_video": {
    "permalink_url": "https://www.facebook.com/reel/1234567890123456/",
    "image": { "uri": "https://example-cdn.fbcdn.net/thumb.jpg" },
    "audio_user_preferred_language": "en"
  },
  "video": {
    "__typename": "Video",
    "playable_duration_in_ms": 15000,
    "embeddable": true
  },
  "attachments": [],
  "tracking": { "top_level_post_id": "1234567890123456" },
  "is_passive_content": false,
  "fb_shorts_reshare_context": {},
  "remix_info": {},
  "soundtrack_info": { "type": "CUSTOM_AUDIO" },
  "track_title": "Example Page · Original audio",
  "music_album_art_uri": "https://example-cdn.fbcdn.net/albumart.png",
  "if_should_change_url_for_reels": { "shareable_url": "https://www.facebook.com/reel/1234567890123456" }
}

Error row examples that may also appear:

• Reel request issue:

  { "inputUrl": "https://www.facebook.com/reel/1234567890123456", "request_error": "RequestException" }
  

• Profile-level failure:

  { "startUrl": "https://www.facebook.com/example/", "error": "Network error", "type": "profile_error" }
  

Notes:

• Some fields (e.g., soundtrack_info, track_title, music_album_art_uri, time) may be empty or null when not present on the page.
• Non-200 responses are surfaced in http_status; parsing issues add parse_error.

FAQ

Do I need a Facebook login or cookies to run this?

No. The actor works with public Facebook Reels and does not require login. For best stability, use a Residential proxy via proxyConfiguration.

How many Reels can I collect per profile?

You control this with resultsLimit, up to 10,000 Reels per profile. The actor processes newest-first where available and streams results to the dataset.

Does it extract likes, comments, or shares?

No. The current output includes captions, publish timestamps, play counts, owner info, and media metadata. Engagement counts like likes/comments/shares are not extracted.

Can I download videos with this?

The output includes playback_video and, when available, videoDeliveryLegacyFields that may contain media URLs you can process downstream. Availability varies by Reel.

Can I use this with Python or an API?

Yes. Run the actor via the Apify API and integrate with your Facebook Reels scraper Python workflows. Export results as JSON/CSV/Excel for pipelines and automation.

Is this a Facebook Reels scraper Chrome extension?

No. It’s a cloud-based Apify actor, more stable than browser extensions and designed for Facebook Reels scraping automation at scale.

Can I filter by date or a rolling window?

Yes. Use onlyPostsNewerThan with absolute dates (YYYY-MM-DD) or relative phrases like “7 days” to skip older Reels.

What if Facebook rate limits or a page fails to fetch?

The actor includes retries and backoff. If an individual Reel fails, you may see request_error or http_status on that row. If a profile run fails, you’ll get a row with error and type=profile_error.

Closing CTA / Final thoughts

Facebook Reels Scraper is built to automate reliable, large-scale extraction of public Facebook Reels metadata and media fields. It helps marketers, developers, analysts, and researchers turn Reel pages into structured records fast.

Set your target profiles, choose a limit, optionally apply a time filter, and stream results straight into an export-ready dataset. Developers can orchestrate runs via the Apify API and plug outputs into Python workflows for end-to-end automation.

Start extracting smarter with a scalable Facebook Reels scraper tool — from quick spot checks to production pipelines.