Facebook Video Details Scraper Advanced
Pricing
from $1.50 / 1,000 results
Facebook Video Details Scraper Advanced
Extract detailed metadata from Facebook videos with Facebook Video Details Scraper Advanced. Submit one or more Facebook video URLs to collect titles, descriptions, views, engagement, uploader data, thumbnails, duration, technical metadata, captions, tags, and more.
Pricing
from $1.50 / 1,000 results
Rating
0.0
(0)
Developer
Alpha Scraper
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
13 days ago
Last modified
Categories
Share
Facebook Video Details Scraper Advanced
The Facebook Video Details Scraper Advanced extracts detailed metadata from Facebook video URLs and returns structured records that can be used for research, content analysis, dataset creation, and automated data workflows.
Provide one or more Facebook video URLs through the actor input, start the run, and review the resulting dataset. Each successfully processed video can include identifying information, title and description, uploader details, engagement metrics, dates, duration, thumbnails, video characteristics, availability information, tags, categories, captions, and other metadata when available from the source.
This Facebook Video Details Scraper Advanced is designed for users who need structured Facebook video metadata rather than manually collecting information from individual video pages. It can be useful for analysts, researchers, marketers, developers, content teams, and other users building repeatable Facebook video data collection workflows.
What Is the Facebook Video Details Scraper Advanced?
The Facebook Video Details Scraper Advanced is an Apify Actor for extracting metadata associated with Facebook video URLs.
The workflow is straightforward: add Facebook video URLs to the required startUrls input, run the Actor, and receive one structured result for each successfully extracted video. The Actor does not download the video itself as its primary output; instead, it collects metadata describing the video and its available media information.
Depending on what is available for a particular Facebook video, a result may contain the video ID, title, description, upload date, views, likes, comments, uploader information, video dimensions, frame rate, duration, thumbnails, tags, categories, captions, live status, language, location, and related metadata.
Some source-dependent fields may not be present for every video. Empty or unavailable values are removed from the final stored record.
Key Features
| Feature | Description | User Benefit |
|---|---|---|
| Facebook video metadata extraction | Processes supplied Facebook video URLs and extracts available video details. | Reduces repetitive manual collection. |
| Multiple URL input | The startUrls field accepts a list containing one or more Facebook video URLs. | Supports batch-oriented collection workflows. |
| Structured results | Extracted information is normalized into named output fields. | Makes results easier to review and analyze. |
| Video engagement data | Results can include views, likes, comments, and repost information when available. | Supports content and engagement research. |
| Uploader information | Records can include uploader name, ID, URL, channel-related data, and creator information when available. | Helps connect videos with publishing entities. |
| Media metadata | Results can contain duration, dimensions, extensions, frame rate, bitrate, formats, and file size when supplied by the source. | Provides useful technical context. |
| Date normalization | Available dates are formatted into consistent date or ISO timestamp representations. | Makes time-based analysis easier. |
| Empty-field cleanup | Missing, null, and empty values are removed before results are stored. | Produces cleaner datasets. |
What Data Can You Extract?
The Actor returns a broad set of Facebook video metadata fields. The exact fields available depend on the source video and the metadata exposed for that video.
Video information
Records can include:
id— Facebook video identifier when available.title— video title.description— available video description.upload_date— normalized upload date.duration— formatted video duration.webpage_url— processed webpage URL.original_url— original or source URL.thumbnail— primary thumbnail URL.thumbnails— available thumbnail information.platform— identifies the platform as Facebook.
Engagement and status
Available records can also contain:
view_countconcurrent_view_countlike_countcomment_countrepost_countlive_statusis_liveavailabilityage_limit
View and concurrent-view values are normalized into compact representations such as 1.2k, 2.5M, or 3.0B when appropriate.
Uploader and creator metadata
The Actor can return:
uploaderuploader_iduploader_urlchannelchannel_idchannel_urlcreatorseriesseason_numberepisode_number
These fields can help organize video records by publisher, creator, or channel-related information when available.
Video and media metadata
Depending on the source, results may include:
extvideo_extformatsfilesizefpswidthheightvbrabrasrhttp_headers
Content and descriptive metadata
The output can additionally include:
tagscategoriessubtitlesautomatic_captionschaptersheatmapcommentarylocationlanguagelicense
Why Use This Actor?
Manually opening Facebook video pages and copying metadata can become repetitive when research involves multiple URLs. The Facebook Video Details Scraper Advanced provides a structured way to collect available information from a list of video URLs in an Apify workflow.
The resulting dataset can support filtering, comparison, categorization, reporting, enrichment, and downstream analysis. Because records use consistent field names, users can work with the data more easily than with manually copied page information.
The Actor is also useful when the primary requirement is metadata collection rather than downloading video files. It focuses on returning information about the supplied videos in a structured record.
Benefits
Structured Facebook video data
Instead of collecting individual values manually, the Actor organizes available metadata into clearly named fields. This is useful for spreadsheets, datasets, analysis workflows, and programmatic processing.
Batch-oriented collection
The required startUrls field accepts multiple URL entries, allowing users to process several Facebook video pages in the same Actor run.
Research support
Video titles, descriptions, creators, engagement metrics, timestamps, URLs, and categories can provide useful inputs for market research, content research, competitive analysis, and dataset development.
Cleaner results
The Actor removes null and empty values before storing records, helping keep output focused on information that is actually available.
How to Use the Facebook Video Details Scraper Advanced
Using the Actor requires only the documented input field.
- Open the Actor and locate the Start URLs input.
- Add one or more Facebook video URLs.
- Make sure the URLs are valid and point to Facebook video pages.
- Start the Actor.
- Review the generated dataset and inspect the fields returned for each video.
- Use the structured results in your research or data workflow.
Start with a small number of URLs so you can confirm that the returned fields meet your requirements before processing a larger collection.
Input
The Actor uses a simple URL-list input model. The documented input schema contains one required field: startUrls.
| Field | Type | Required | Description |
|---|---|---|---|
startUrls | Array | Yes | List of one or more Facebook video URLs to process. |
The input is presented through Apify's request-list interface. Each list item should contain a url value representing the Facebook video page you want to process.
Input Example
{"startUrls": [{"url": "https://www.facebook.com/watch?v=25092205360464027"},{"url": "https://www.facebook.com/watch?v=1550027399351699"}]}
Use actual Facebook video URLs in your run. The sample URLs above illustrate the expected structure of the configured input.
Output
The Actor stores one normalized record for each video successfully extracted. It also maintains a consolidated collection of successfully processed records for the run.
Unavailable values are omitted from individual output records. Therefore, two videos may contain different subsets of fields depending on the metadata available for each source.
Dates are normalized where the source provides recognizable date information. Duration values are formatted into readable strings such as 45s, 3m 20s, or 1h 5m.
Output Fields
| Field | Description |
|---|---|
id | Video identifier. |
title | Video title. |
upload_date | Normalized upload date. |
description | Video description. |
view_count | Formatted view count when available. |
concurrent_view_count | Formatted concurrent viewer count when available. |
uploader | Uploader name. |
uploader_id | Uploader identifier. |
platform | Platform identifier, set to facebook. |
webpage_url | Video webpage URL. |
original_url | Original supplied/source URL. |
timestamp | Normalized timestamp date. |
timestamp_iso | ISO-formatted timestamp. |
duration | Formatted duration. |
thumbnail | Primary thumbnail URL. |
thumbnails | Available thumbnail metadata. |
ext / video_ext | Media extension information. |
formats | Available format metadata. |
fps | Frame rate when available. |
width / height | Video dimensions. |
vbr / abr / asr | Video, audio, and audio-sampling metadata when available. |
filesize | Available file-size information. |
like_count / comment_count / repost_count | Engagement metrics. |
live_status / is_live | Live-video status information. |
uploader_url | Uploader webpage URL. |
channel / channel_id / channel_url | Channel-related metadata when available. |
release_timestamp / release_timestamp_iso | Release timestamp information. |
tags / categories | Content classification metadata. |
subtitles / automatic_captions | Available caption information. |
chapters / heatmap | Additional video metadata when available. |
availability | Source availability information. |
location | Location metadata when available. |
language | Language metadata when available. |
license | License metadata when available. |
Output Example
{"id": "25092205360464027","title": "Example Facebook Video","upload_date": "2026-09-18","description": "Example video description","view_count": "12.4k","like_count": 420,"comment_count": 38,"uploader": "Example Creator","uploader_id": "123456789","platform": "facebook","webpage_url": "https://www.facebook.com/watch?v=25092205360464027","original_url": "https://www.facebook.com/watch?v=25092205360464027","timestamp": "2026-09-18","timestamp_iso": "2026-09-18T12:30:00Z","duration": "3m 25s","thumbnail": "https://example.com/thumbnail.jpg","fps": 30,"width": 1280,"height": 720,"like_count": 420,"comment_count": 38,"tags": ["example","video"],"categories": ["Entertainment"],"language": "en","is_live": false}
The example demonstrates the structure and formatting of a possible result. Actual fields vary according to the information available for the processed video.
Use Cases
The Facebook Video Details Scraper Advanced can support several practical workflows:
- Content research: Collect titles, descriptions, publication dates, creators, and available content metadata for analysis.
- Competitive research: Organize public-facing video metadata across selected Facebook video URLs.
- Engagement analysis: Review available view, like, comment, repost, and live-status information.
- Dataset creation: Build structured collections of Facebook video records for further research or analysis.
- Creator research: Connect videos with uploader, creator, and channel-related information.
- Media analysis: Examine duration, dimensions, frame rate, formats, thumbnails, and other available technical metadata.
- Research automation: Repeat URL-based metadata collection through an Apify workflow instead of manually gathering each record.
Advantages and Practical Strengths
This Actor provides a focused workflow for users who already have Facebook video URLs and need structured metadata from those pages. Its simple input model reduces configuration overhead, while the normalized output combines descriptive, engagement, publisher, temporal, and media-related information in a single record.
The range of possible metadata fields also makes the output useful beyond simple title extraction. Depending on source availability, users can inspect both content information and technical video characteristics.
Limitations
Results depend on the metadata that can be obtained for each supplied Facebook video URL. Not every video necessarily provides every possible field.
Important considerations include:
- Some fields may be absent when the source does not provide them.
- An unsuccessful or inaccessible video may produce no usable record.
- Metadata availability can vary between videos.
- The Actor is designed around Facebook video URLs provided through
startUrls. - Technical media fields such as formats, bitrate, frame rate, or file size may not be available for every result.
- Captions, tags, chapters, heatmap information, and related fields are source-dependent.
The Actor does not guarantee that every possible metadata field will be returned for every Facebook video.
Pros and Cons
| Pros | Cons |
|---|---|
| Supports multiple Facebook video URLs in one configured input. | Available metadata can vary by video. |
| Returns structured fields covering content, engagement, creator, and media information. | Some results may omit optional fields. |
| Automatically removes null and empty values from stored records. | Videos that cannot be processed may return no record. |
| Provides normalized date and duration representations. | Technical metadata is not guaranteed for every source. |
| Suitable for repeatable data-collection workflows. | Requires valid Facebook video URL inputs. |
Comparison With Manual Collection
| Capability | This Actor | Manual / Typical Alternative |
|---|---|---|
| Multiple video URLs | Supported through startUrls | Usually handled one page at a time |
| Structured output | Normalized dataset records | Requires manual formatting |
| Engagement metadata | Returned when available | Must be copied manually |
| Creator and uploader fields | Returned when available | Requires individual inspection |
| Video technical metadata | Available fields can be collected with the record | May require separate manual inspection |
| Reusable workflow | Suitable for repeatable Apify runs | More repetitive manual work |
This comparison describes workflow characteristics rather than guaranteeing that every manual alternative behaves the same way.
Best Practices
For consistent results, begin with a small test set of Facebook video URLs and inspect the resulting records. This helps you understand which fields are available for your particular videos.
Use valid Facebook video URLs and keep the startUrls structure aligned with the documented input schema. For larger research projects, review a sample of returned records before relying on the dataset for analysis.
When a field is missing, treat it as unavailable rather than assuming that a blank value represents zero. Engagement values, captions, technical properties, and other metadata can vary across videos.
For important research datasets, validate key fields such as title, URL, creator, and engagement information before using them in downstream analysis.
Troubleshooting
Invalid Input
Check that each startUrls entry contains a valid url value and that the URL refers to a Facebook video page. Ensure the JSON structure matches the documented example.
Empty Results
Verify the supplied URLs and try a small test run with a known Facebook video URL. An empty result can occur when usable metadata cannot be obtained for the supplied page.
Partial Results
Partial metadata is expected when certain information is unavailable for a particular video. Review the fields returned for the individual record rather than expecting every field to exist for every URL.
Missing Fields
The Actor removes unavailable values from the final record. A missing field therefore indicates that the corresponding information was not available in the extracted metadata for that video.
Temporary Failures
Retrying a run with valid inputs can help distinguish a temporary processing issue from a source-specific availability problem. Review Actor logs when a particular URL repeatedly fails.
Frequently Asked Questions
What does the Facebook Video Details Scraper Advanced do?
It extracts structured metadata from supplied Facebook video URLs and stores successfully processed records in the Actor's output dataset.
What input does the Facebook Video Details Scraper Advanced require?
The documented input requires startUrls, an array containing one or more Facebook video URL entries.
Can I process multiple Facebook videos?
Yes. The startUrls input is an array, so multiple Facebook video URLs can be provided in a single run.
What data can the Actor extract?
Possible fields include video ID, title, description, dates, views, likes, comments, uploader information, thumbnails, duration, dimensions, formats, captions, tags, categories, live status, language, and other available metadata.
Does every result contain every output field?
No. Output depends on the metadata available for each individual video. Empty or unavailable values are omitted from stored records.
How is duration represented?
Duration is converted into a readable format such as seconds, minutes and seconds, or hours and minutes.
How are view counts represented?
Large view and concurrent-view values are shortened into readable formats such as 1.2k, 2.5M, or 3.0B.
Is this Actor suitable for research workflows?
Yes. The structured output can be used for content research, creator research, engagement analysis, competitive research, and dataset creation involving supplied Facebook video URLs.
What should I do when a video returns incomplete metadata?
Review the fields that were returned and treat missing fields as unavailable. Testing several URLs can help you understand metadata coverage for your particular collection.
Should I start with a small run?
Yes. A small test run is a practical way to validate the input format and inspect the resulting dataset before processing a larger list of URLs.
NLP Keywords
- Facebook video metadata
- Facebook video data extraction
- Facebook video information
- Facebook video details
- video metadata scraper
- Facebook video scraper
- Facebook video extractor
- Facebook video URL extraction
- Facebook video dataset
- Facebook video analytics data
- video engagement metadata
- Facebook video uploader data
- Facebook video technical metadata
- video title extraction
- video description extraction
- video thumbnail metadata
- video duration metadata
- Facebook creator information
- structured video data
- social video research
Related Keywords
- Facebook video details scraper
- Facebook video metadata extractor
- scrape Facebook video information
- extract Facebook video details
- Facebook video data scraper
- Facebook video URL scraper
- Facebook video analytics scraper
- Facebook video content metadata
- Facebook video engagement data
- Facebook video creator data
- Facebook video title and description scraper
- Facebook video thumbnail scraper
- Facebook video duration extractor
- Facebook video technical information
- Facebook video research tool
- Facebook video dataset builder
- extract metadata from Facebook videos
- collect Facebook video metadata
- structured Facebook video data
- automate Facebook video data collection
Final Overview
The Facebook Video Details Scraper Advanced provides a structured way to collect available metadata from one or more Facebook video URLs. Instead of manually reviewing individual video pages, users can submit a list of URLs and receive organized records containing relevant video, creator, engagement, date, content, and media information when available.
Its straightforward startUrls input makes the Actor accessible for both small research tasks and repeatable URL-based collection workflows. Because missing values are removed and available metadata is normalized into consistent fields, the resulting dataset can be easier to review, filter, analyze, and reuse.
For the most reliable workflow, begin with a small set of valid Facebook video URLs, inspect the returned fields, and then expand your collection according to the metadata requirements of your project.
Contact me: Alphascraper69@gmail.com


