Facebook Page Video Downloader avatar

Facebook Page Video Downloader

Pricing

from $0.50 / 1,000 video result saveds

Go to Apify Store
Facebook Page Video Downloader

Facebook Page Video Downloader

Discover videos from public Facebook Page Videos and Reels tabs, paginate and deduplicate results, and save bounded MP4 files with source metadata and download status.

Pricing

from $0.50 / 1,000 video result saveds

Rating

0.0

(0)

Developer

Khadin Akbar

Khadin Akbar

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Share

Find videos from public Facebook Page Videos and Reels tabs, then save available MP4 copies with captions, source links and download status. Start with a Page URL; get one Dataset row per unique video and a saved-file URL when downloading succeeds. Native discovery uses Apify US residential proxy and has no scan-event charge. Video results and automatic startup events are billed, with Apify platform usage additional.

What it does

  • Discover Page videos without collecting individual post links first.
  • Paginate through the Videos listing, Reels grid, or both; combine up to ten Pages and deduplicate by video ID.
  • Return available progressive SD/HD MP4 addresses, captions, publish times and public counts.
  • Save complete MP4 files within per-file and combined saved-byte limits.

Example workflow

Use this Actor when you need an authorized Page-video archive, an editorial clip review, or a Page-level video analysis workflow. For example, an editor can request twelve recent public videos from a publisher, save small SD copies, then export source links and download outcomes for review.

Avoid this Actor when you need private content, individual-video URL downloads, complete historical coverage or permanent file hosting.

Accepts Page home URLs and Videos/Reels tab URLs. It does not accept individual video URLs, groups or private content. It uses content Facebook exposes without a login, with an anonymous source session kept only in process memory. A requested maximum is a cap, not a guarantee that every historical video is accessible.

Quick start

{
"pageUrls": ["https://www.facebook.com/NASA/"],
"mode": "feed",
"maxVideos": 3,
"maxScans": 2,
"downloadMp4": true,
"quality": "sd",
"maxFileSizeMB": 25,
"maxTotalDownloadMB": 100
}

The stable API value feed now reads the Page's public Videos tab. Choose reels for the Reels grid or both for both sources. Set downloadMp4 to false to export media links without saving files.

Input settings

SettingDefaultEffect
pageUrlsRequired1–10 public Page URLs; duplicate URLs are combined
modefeedVideos tab, Reels tab, or both
maxVideos10Unique result cap across all Pages; maximum 100
maxScans2Discovery-page cap across all sources; maximum 50
downloadMp4trueSave available complete MP4 copies
qualitysdPrefer SD, or hd when exposed; use available quality if the preference is absent
maxFileSizeMB25Single saved-file limit in MiB; maximum 100
maxTotalDownloadMB100Combined saved-file limit in MiB; maximum 500

One MiB is 1,048,576 bytes. Transfer consumed before an oversized or interrupted response stops can still incur platform usage. The saved-byte cap does not cap every attempted network byte. Progressive MP4 files are supported; separate audio/video streams and manifests are not joined.

Output fields

FieldsMeaning
videoId, pageUrl, videoUrl, mediaTypeStable identity, input Page, source permalink and video/Reel type
downloadUrl, sdDownloadUrl, hdDownloadUrlExposed MP4 addresses; signed source links can expire
caption, authorName, postedAtPublic metadata where exposed; missing values remain null
durationSeconds, reactionCount, viewCount, viewCountSourceMedia/count values with source; Reels badge counts may be rounded
storedMp4Url, storedBytes, downloadStatusSaved-file location and outcome; a result can remain useful without a saved copy
discoveryMode, provider, scrapedAtSource selection, native route and retrieval timestamp

A shortened source-record example:

{
"videoId": "1803909017420449",
"pageUrl": "https://www.facebook.com/NASA/",
"videoUrl": "https://www.facebook.com/watch/?v=1803909017420449",
"mediaType": "video",
"provider": "native-facebook",
"storedMp4Url": null,
"storedBytes": 0,
"downloadStatus": "not_requested"
}

OUTPUT and RUN_SUMMARY explain the outcome, delivered videos, saved files, requests, accepted named events, effective event prices and warnings. An unavailable source is classified as UPSTREAM_FAILED when no useful row was saved. A completed source with genuinely no matches is VALID_EMPTY. A spending limit that prevents any result returns actionable limit diagnostics, rather than a useful partial-result label.

Pricing and spending limits

Check the live Pricing tab for effective fees. Pay per event applies: current native builds charge startup plus saved video results, without discovery-page events:

Buyer tierPer video10 videos plus one start, before usage
Free, Bronze, Silver, Gold, Platinum and Diamond$0.0005$0.0051

Startup is $0.0001 per automatic memory-scaled unit, minimum one. Restarts/resurrections can add startup units. Empty or unavailable-source runs can still incur startup and platform usage. A video-result event includes a bounded file attempt and is charged for the saved video metadata/link record even if the MP4 is oversized or unavailable. There is no separate saved-file event.

For example, 10 rows of saved video metadata at the flat rate cost $0.0051 in Actor events, plus your platform compute, proxy, transfer and storage usage.

Total cost is startup units × startup price + saved video rows × your result price + platform usage. Native discovery has no paid external lookup; Apify residential proxy bandwidth is additional platform usage at the caller’s applicable residential rate and requires access to Apify Proxy. The Pricing tab retains a legacy discovery event for older provider-backed builds; current native builds never charge it.

Set a maximum event charge when starting a run and choose video/scan/byte limits. An event cap does not cap all platform transfer, compute or storage costs. Retained files and later reads also consume usage. Files follow run-storage retention; this is not permanent hosting.

API example

curl --request POST \
'https://api.apify.com/v2/acts/khadinakbar~facebook-page-video-downloader/runs' \
--header "Authorization: Bearer $APIFY_TOKEN" \
--header 'Content-Type: application/json' \
--data '{"pageUrls":["https://www.facebook.com/NASA/"],"maxVideos":1,"maxScans":1,"downloadMp4":true}'

Poll the returned run ID. After completion, export /v2/datasets/<defaultDatasetId>/items, read /v2/key-value-stores/<defaultKeyValueStoreId>/records/RUN_SUMMARY, and open each saved row's storedMp4Url. Keep credentials in the authorization header.

AI agent prompt

Find up to three public videos from this Facebook Page. Scan at most two discovery pages, save SD MP4 copies no larger than 25 MiB each, and return source links, saved-file URLs and download warnings.

Best results and recovery

  • Start with a small request for a Page visible while logged out.
  • Increase maxScans for more pages; check the summary for caps and source failures.
  • Prefer SD when file size matters. HD availability and historical coverage depend on the source.
  • Treat direct media links as temporary. Download a saved copy before run storage expires.
  • Interruption leaves a record of pending effects. Inspect STATE before resuming ambiguous work; the Actor refuses to replay uncertain persistence or charges automatically.

Verification and freshness

Checked 2026-10-26 using public Page samples, parser fixtures and saved SD/HD MP4 decoding. Checks cover source identity, distinct video IDs, metadata, cursor parsing, size limits and named-event accounting. A bounded sample does not establish population-wide reliability; availability can change with Facebook responses.

Builder's note

Engineering evidence is dated October 26, 2026. Each release is checked against its immutable cloud build with saved Dataset rows, named-event counts and run summaries; this describes a bounded QA sample. In my testing, the native route returned distinct videos on successive pages. I designed it to read public listings and pagination data exposed by the Page. That removes the external lookup bill and finds Videos-tab content directly, rather than scanning photo/text posts for videos. Facebook can change its response shape or restrict a Page; the summary preserves that unavailability instead of inventing an empty success. Acceptance results describe the tested sample; population-wide reliability remains unmeasured.

Source and responsible use

This independent Actor is not affiliated with or endorsed by Meta or Facebook. Use it for content you own or have authority to collect and retain. Public accessibility does not grant copyright or other reuse rights. Respect applicable terms, privacy requirements and retention obligations. The Actor does not use login credentials or bypass authentication.