Faacebook Video Scraper Pro
Pricing
$9.99/month + usage
Go to Apify Store
🤔 What I inferred from
Faacebook Video Scraper Pro
Powerful Facebook Reels & Video Scraper built for speed and reliability. Instantly scrape public reels & videos, extract clean metadata, and store the final MP4 directly in Apify Key-Value Store for instant access. Zero setup, proxy-ready, enterprise-safe. Click Run & get usable videos in seconds.
Pricing
$9.99/month + usage
Rating
0.0
(0)
Developer
Neuro Scraper
Maintained by Community
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Facebook Video & Reels Scraper Pro
One-liner: Download Facebook videos (MP4/AVC preferred), normalize metadata, and store results to Apify Dataset & Key-Value Store — plug-and-play on Apify Console.
Outcome-focused: Get clean video files and normalized metadata in seconds — ready for analytics, republishing, or archiving.
📖 What this Actor does (short)
This Actor extracts rich metadata for Facebook videos and downloads media with a bias toward H.264/AVC formats for widest compatibility. It produces a structured Dataset entry for each input URL and saves the final media to the Actor Key-Value Store (with local fallback). Built for speed, reliability, and safe operation on Apify Console.
💡 Use cases / When to use
- Bulk-archive public Facebook videos for research or compliance.
- Fetch normalized metadata (title, uploader, timestamps, counts) for analytics pipelines.
- Convert or preserve playable MP4s (H.264) for distribution or ingestion.
- Rapid single-URL exports via Console for one-off downloads.
⚡ Quick Start (Console — one-click)
- Open this Actor in Apify Console.
- Paste one or more Facebook video URLs into the Input field.
- Optionally enable Apify Proxy in the Console input.
- Click Run — results appear in Dataset and media in Key-Value Store.
Demo visual: Add a short GIF or screenshot here to increase conversion.
⚙️ Quick Start (CLI + API)
CLI (apify-cli one-liner)
Python — apify-client (compact)
📝 Inputs (fields & schema)
Below is the inferred input schema. The Console accepts JSON with these keys.
Console JSON example — also saved as input.example.json in this package.
(See input.example.json file for a minimal run-ready example.)
Inferred schema (short)
⚙️ Configuration (friendly table)
| 🔑 Name | 📝 Type | ❓ Required | ⚙️ Default | 📌 Example | 🧠 Notes |
|---|---|---|---|---|---|
| startUrls | array | ✅ Yes | [] | ["https://..."] | One or more Facebook video URLs (or provide url). |
| url / startUrl | string | ⚠️ Optional | None | "https://..." | Single URL alias. |
| download | boolean | ⚙️ Optional | false | true | If true, Actor attempts to download media. |
| download_merged | boolean | ⚙️ Optional | true | true | Prefer merged video+audio file (mp4). |
| desired_resolution | string | ⚙️ Optional | "1080p" | "720p" | Preferred target resolution (e.g. 1080p). |
| preserve_downloads | boolean | ⚙️ Optional | false | true | Keep local copies after upload to KV. |
| cookiesFile / cookie_file | string | ⚙️ Optional | None | "COOKIES.txt" | Path in actor storage to cookies file (if needed). |
| proxyConfiguration | object | ⚙️ Optional | {"useApifyProxy": true} | {"useApifyProxy": false, "country": "US"} | Console proxy settings. |
| maxConcurrency | integer | ⚙️ Optional | 5 | 10 | Controls parallel downloads (1–50). |
| maxRetries | integer | ⚙️ Optional | TODO: confirm | 2 | TODO: inferred — confirm retry policy. |
Console setup hint: Paste an array of URLs into startUrls (or a single URL into url), adjust download and desired_resolution, then Run.
📄 Outputs (Dataset / KV examples)
This Actor writes two primary outputs:
- Dataset — JSON entries for each processed URL (metadata + links)
- Key-Value Store (KV) — binary media files stored under stable keys; Actor also sets
ALL_RESULTSandOUTPUTkeys for convenience.
Example Dataset entry (trimmed)
Notes:
kv_files.final.kv_keyis the Key-Value Store record name for the media file.download_links.final_direct_urlis available when run on Apify Console and the KV write succeeded.
🔑 Environment Variables
Use Console secrets or the apify-client to provide the token.
APIFY_TOKEN— your Apify API token (use Console secret storage or placeholder<APIFY_TOKEN>).HTTP_PROXY,HTTPS_PROXY— optional for custom proxying (<PROXY_USER:PASS@HOST:PORT>).
Important: Never commit secrets in plain text. Use Console secret fields.
▶️ How to Run (step-by-step)
In Apify Console
- Open the Actor page.
- Paste JSON input (see
input.example.json). - (Optional) Enable Apify Proxy in the Console or supply
proxyConfigurationin input. - Click Run.
- Inspect Logs, Dataset, and Key-Value Store when the job finishes.
From CLI
Via API (apify-client) — See Quick Start above for compact example.
⏰ Scheduling & Webhooks
- Schedule: Use Apify Console schedule to run this Actor hourly/daily — ideal for regular archives.
- Webhooks: Configure a webhook in the Console to receive run completion notifications or to trigger downstream jobs.
🕾️ Logs & Troubleshooting
Where to find logs: Actor run Logs tab in Apify Console.
Common issues & fixes
- No startUrls provided — ensure
startUrlsorurlis present in input. - Download failed — try toggling proxy, verify cookies file if the video is age-restricted.
- Large uploads failing — increase memory on run or enable Apify Proxy; check KV size limits.
Quick fixes:
- Re-run with
download=falseto only fetch metadata. - Set
preserve_downloads=trueto keep local copies for debugging.
🔒 Permissions & Storage Notes
- Writes: Dataset, Key-Value Store (media files), and Actor values
ALL_RESULTSandOUTPUT. - Privacy: Designed to operate on public media — do not use for unauthorized automated access. Always respect platform TOS and copyright.
🔟 Changelog / Versioning
v1.0.0 — Initial Console-ready release. Includes metadata normalization, H.264-first downloads, KV storage, and dataset output.
🖌 Notes / TODOs
- TODO: confirm
maxRetriesand other hidden retry defaults — not explicit in input schema. - TODO: add a short demo GIF and one high-resolution screenshot to improve conversions.
🌍 Proxy Configuration
Enable Apify Proxy (Console): Turn on the Use Apify Proxy toggle in the Actor run dialog (or set proxyConfiguration.useApifyProxy to true in input).
Custom proxy example (secrets):
- HTTP_PROXY:
<PROXY_USER:PASS@HOST:PORT> - HTTPS_PROXY:
<PROXY_USER:PASS@HOST:PORT>
Notes:
- Store credentials as Console secrets — do not paste in the input JSON.
- Example input snippet for custom proxy:
TODO: Consider proxy rotation for large-scale scraping.
📚 References (official Apify docs)
🤔 What I inferred from main.py
- Network usage: YES — Actor performs remote extraction and media downloads (Proxy section included).
- Primary inputs:
startUrls/url,download,desired_resolution,cookiesFile,proxyConfiguration,maxConcurrency. - Outputs: Dataset entries with normalized metadata, Key-Value Store media files,
ALL_RESULTSandOUTPUTactor values. - Scheduling: supports parallel runs via
maxConcurrencyand is suitable for scheduled archival runs.
✅ Why this Actor (short benefits)
- Production-ready: Designed for bulk runs with concurrency controls.
- Compatibility-first: Prefers H.264/AVC files for the broadest playback support.
- Plug & play: Run on Apify Console with minimal input and instant results.
- Safe-by-design: Uses Console secrets for credentials and optional proxy handling.
Run this Actor on Apify Console — get instant results in seconds.
input.example.json
CONFIG.md (optional)
Quick configuration tips
- Use
download=falseto only fetch metadata for validation runs. - Use
preserve_downloads=trueif you need local copies for debugging. - Reduce
maxConcurrencyon small plans to avoid throttling (e.g. set to 1–3).
Advanced proxy notes
- For stable large-scale runs, prefer
useApifyProxyvia Console toggle. - If using custom proxies, rotate credentials outside the Actor and pass a single working proxy URL in input.
Limitations & recommended checks
- Actor expects publicly accessible Facebook videos. Age-restricted or login-required content may need valid cookies.
- KV storage has limits per Apify account — consider external storage for large archives.
