# Facebook reels Downloader Audio or Video - Separate (`alpha-scraper/facebook-reels-downloader-audio-or-video-separate`) Actor Facebook Reels Downloader Audio or Video - Separate extracts Facebook Reel metadata and available video and audio URLs from one or multiple Reel links. Get structured title, duration, description, thumbnail, media URLs, and format details. - **URL**: https://apify.com/alpha-scraper/facebook-reels-downloader-audio-or-video-separate.md - **Developed by:** [Alpha Scraper](https://apify.com/alpha-scraper) (community) - **Categories:** Social media, Videos, Other - **Stats:** 3 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $1.50 / 1,000 results This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ### Facebook Reels Downloader Audio or Video - Separate Facebook Reels Downloader Audio or Video - Separate is an Apify Actor for extracting Facebook Reels metadata and returning available video and audio media URLs in structured dataset records. It accepts one or multiple Facebook Reels share links or URLs and processes each supplied URL individually. The Actor is designed for users who need Facebook Reel information together with accessible media URLs for video or audio workflows. Each successful result can include the Reel title, duration, description, thumbnail URL, video download URL, and audio download URL. Additional format and source metadata is also returned when available. The Actor does not store downloaded media files as its primary output. Instead, it returns the available media URLs so users can use the resulting dataset in their own workflow. ### What Is the Facebook Reels Downloader Audio or Video - Separate? This Facebook Reels Downloader is focused on Facebook Reels URL processing. You provide Facebook Reel URLs through the `startUrls` input, and the Actor returns structured information for each URL. The workflow is straightforward: 1. Provide one or multiple Facebook Reels URLs. 2. Start the Actor. 3. The Actor processes each URL. 4. A result record is added to the default dataset for each processed URL. 5. Review the metadata and available video or audio URLs. When separate video and audio streams are available, the corresponding fields can contain different media URLs. When separate streams are not available, the Actor can use an available combined media format as a fallback. ### Key Features | Feature | Description | User Benefit | | -------------------------- | ------------------------------------------------------------------ | -------------------------------------------- | | Facebook Reels URL input | Accepts one or multiple Facebook Reels URLs | Process multiple Reel links in a single run | | Reel metadata extraction | Returns title, duration, description, and thumbnail information | Provides useful context alongside media URLs | | Video media URL | Returns an available video URL when one can be identified | Supports video-focused workflows | | Audio media URL | Returns an available audio URL when one can be identified | Supports audio-focused workflows | | Separate stream preference | Uses available video-only and audio-only formats when present | Helps keep video and audio access distinct | | Combined format fallback | Uses a combined format when separate media streams are unavailable | Provides a fallback media URL when possible | | Structured dataset output | Pushes records to the default Apify dataset | Makes results easier to inspect and process | | Error records | Returns the source URL and error message when extraction fails | Helps identify inputs that need attention | ### What Data Can You Extract? A successful result can contain several useful categories of Facebook Reel data. **Reel information** includes the original input URL, title, duration, and description when available. **Visual information** includes the Reel thumbnail URL, allowing users to retain a visual reference for the processed content. **Media information** includes `video_download_url` and `audio_download_url`. These fields represent the available media URLs identified for the Reel. Depending on the source data, separate video and audio streams may be available, or a combined media URL may be used as a fallback. **Format information** is provided through `_best_video_format` and `_best_audio_format` when suitable formats are identified. These objects can include format ID, extension, resolution, or audio bitrate information. **Source information** is available through `_raw_info`, which can contain the source ID, uploader, and webpage URL when those values are available. When extraction fails for an individual URL, the dataset can instead contain the original `url` and an `error` message for that item. ### Why Use This Actor? A Facebook Reels Downloader can be useful when manually opening and processing many Reel URLs would create repetitive work. Instead of collecting metadata and media links one by one, users can provide a list of URLs and receive structured records in one Apify dataset. The Actor is particularly useful when the goal is organized data collection rather than simply viewing a Reel. The returned fields can support research, content workflows, media organization, dataset creation, and downstream automation. Because the Actor returns structured records, users can inspect individual fields without manually copying information from each Facebook Reel page. ### Benefits This Actor provides practical benefits for URL-based Facebook Reel research and media workflows: - **Multiple URL processing:** Submit one or multiple Reel URLs in the same run. - **Structured results:** Metadata and media URLs are returned as consistent dataset fields. - **Video and audio access:** Separate fields are provided for video and audio media URLs. - **Metadata preservation:** Title, duration, description, and thumbnail information can be retained with the result. - **Automation-friendly workflow:** Suitable for repeatable Apify-based data collection workflows. - **Error visibility:** Failed URL processing can produce an error record instead of silently disappearing. - **Dataset-oriented output:** Results are pushed to the default Apify dataset for convenient review and further use. ### How to Use the Facebook Reels Downloader Audio or Video - Separate Using the Actor requires only the supported URL input. 1. Open the Actor input page. 2. Add one or more Facebook Reels URLs to `startUrls`. 3. Confirm that every entry contains a valid `url`. 4. Start the Actor. 5. Open the default dataset after processing. 6. Review the returned metadata and available media URLs. For an initial test, start with a small number of URLs. This makes it easier to verify that the supplied links are appropriate and that the resulting dataset contains the fields you need. ### Input The documented input schema contains one required field: `startUrls`. | Field | Type | Required | Description | | ----------- | ----- | -------- | ------------------------------------------------------------------------------- | | `startUrls` | Array | Yes | One or multiple Facebook Reels URL objects. Each object contains a `url` value. | The intended input format is a request-list style array containing URL objects. The Actor also handles string entries internally, but the documented Apify input schema uses URL objects. Supported examples include Facebook Reel URLs such as standard `/reel/` links and Facebook share links that point to Reels. ### Input Example ```json { "startUrls": [ { "url": "https://www.facebook.com/reel/1289152909325322" }, { "url": "https://www.facebook.com/reel/1606805090910208" }, { "url": "https://www.facebook.com/share/r/1GyTpE9i72/" } ] } ``` ### Output The Actor writes processed records to the default Apify dataset. A successful Facebook Reels Downloader result can include the original URL, Reel metadata, thumbnail information, video and audio media URLs, selected format details, and source information. The availability of individual values depends on what can be obtained for the supplied Reel URL. A field can therefore contain a value or `null`. If extraction fails for a specific URL, the Actor can create a record containing the URL and an `error` field rather than the normal successful-result structure. ### Output Fields | Field | Description | | -------------------- | ------------------------------------------------------------------------------------------------- | | `url` | The original Facebook Reel URL supplied as input. | | `title` | Reel title when available. | | `duration` | Reel duration when available. | | `description` | Reel description when available. | | `thumbnail_url` | Thumbnail URL associated with the Reel when available. | | `video_download_url` | Available video media URL, when identified. | | `audio_download_url` | Available audio media URL, when identified. | | `_best_video_format` | Details of the selected video format, including format ID, extension, and height when available. | | `_best_audio_format` | Details of the selected audio format, including format ID, extension, and bitrate when available. | | `_raw_info` | Additional source information such as source ID, uploader, and webpage URL when available. | | `error` | Error message for a URL when processing that individual input fails. | The underscore-prefixed fields are additional metadata included in the actual Actor result and can be useful for users who need more context about the selected media formats or source record. ### Output Example ```json { "url": "https://www.facebook.com/reel/1289152909325322", "title": "Example Facebook Reel", "duration": 42, "description": "Example Reel description", "thumbnail_url": "https://example.com/thumbnail.jpg", "video_download_url": "https://example.com/video.mp4", "audio_download_url": "https://example.com/audio.m4a", "_best_video_format": { "id": "video-format-id", "ext": "mp4", "height": 1080 }, "_best_audio_format": { "id": "audio-format-id", "ext": "m4a", "abr": 128 }, "_raw_info": { "id": "example-id", "uploader": "Example Uploader", "webpage_url": "https://www.facebook.com/reel/1289152909325322" } } ``` ### Use Cases The Facebook Reels Downloader Audio or Video - Separate can support several practical workflows: - **Content research:** Collect Reel metadata and media URLs for organized content analysis. - **Media cataloging:** Build datasets containing Reel titles, durations, thumbnails, and media references. - **Market research:** Gather publicly accessible Reel information for research projects. - **Content analysis:** Preserve descriptions and source information alongside collected media URLs. - **Dataset creation:** Create structured Facebook Reel datasets for later review or processing. - **Workflow automation:** Process batches of known Reel URLs through an Apify workflow. - **Media organization:** Separate video-oriented and audio-oriented result fields for downstream handling. Users should ensure that their intended use of collected content and URLs complies with Facebook's applicable terms, copyright rules, and other relevant requirements. ### Factual Competitive Advantages The practical strengths of this Actor come from its focused workflow. It combines URL-based Reel processing with structured metadata and separate media URL fields in a single dataset record. The Actor also provides format-related metadata when available, giving users additional context beyond a basic URL-only result. Its per-URL error records can further help identify inputs that did not process successfully. These are functional characteristics of the Actor, rather than claims that it is universally better than other approaches. ### Pros and Cons | Pros | Cons | | ------------------------------------------- | -------------------------------------------------------------------------------- | | Supports multiple Facebook Reels URLs | It returns media URLs rather than storing downloaded files as the primary output | | Provides both metadata and media URL fields | Individual fields may be unavailable for some inputs | | Includes video and audio URL fields | Separate video/audio streams are not guaranteed | | Provides format details when available | A failed URL can return an error instead of a normal result | | Structured Apify dataset output | Results depend on the supplied Facebook Reel URL and available source data | ### Comparison With Alternative Approaches | Capability | This Actor | Manual / Typical Alternative | | ---------------------------- | -------------------------------- | -------------------------------------------- | | Multiple Reel URL processing | Supported | Often requires repeating the task manually | | Structured dataset records | Supported | May require manual collection and formatting | | Reel metadata collection | Supported | Usually copied or recorded manually | | Video and audio URL fields | Supported where available | Requires separate manual inspection | | Per-URL error visibility | Supported through result records | Often tracked separately | | Repeatable Apify workflow | Supported | Usually more manual | This comparison describes workflow differences rather than overall product superiority. ### Limitations The Actor has several important practical limitations: - A valid-looking Facebook Reel URL does not guarantee that every metadata or media field will be available. - Separate audio and video streams may not always be found. - When separate streams are unavailable, the Actor can fall back to a combined media format. - Processing failures are reported on an individual URL basis through an error record. - Returned values such as title, description, uploader information, and thumbnails depend on the information available for the processed Reel. - The Actor provides media URLs rather than a primary downloaded-file archive in the Apify dataset. These limitations mean that important results should be reviewed before being used in workflows that require complete or persistent media availability. ### Best Practices For a reliable user workflow, consider the following practices: - Start with a small batch of known Facebook Reel URLs. - Use the documented `startUrls` structure. - Verify that each URL points to the intended Facebook Reel. - Review dataset results after a test run. - Check `video_download_url` and `audio_download_url` before assuming both streams are available. - Use the metadata fields together with the original `url` for easier record identification. - Monitor records containing `error` so unsuccessful inputs can be reviewed separately. - Validate important collected information before using it in business, research, or automated processes. ### Troubleshooting **Invalid Input** Check that `startUrls` is present and contains URL objects with a non-empty `url` value. Use valid Facebook Reel links rather than unrelated page URLs. **Empty or Missing Media URLs** Review the processed record to see whether the relevant media URL is `null`. Not every source response necessarily provides both separate audio and video streams. **Partial Results** A Reel may return some metadata fields while other values are unavailable. Review the complete record instead of assuming that a missing field indicates total processing failure. **Missing Metadata** Title, description, thumbnail, uploader, and related values depend on the information available for the supplied URL. Missing values can therefore occur without all processing having failed. **Extraction Error** When a URL cannot be processed, inspect the corresponding `error` field and verify that the original URL is valid. Retesting with a known accessible Reel URL can help distinguish an input-specific problem from a broader issue. ### Frequently Asked Questions **What does the Facebook Reels Downloader Audio or Video - Separate do?** It processes Facebook Reels URLs and returns structured Reel metadata together with available video and audio media URLs. **What input does the Facebook Reels Downloader use?** The documented input is `startUrls`, an array containing one or multiple objects with a `url` field. **Can I process multiple Facebook Reels in one run?** Yes. The `startUrls` field is designed for one or multiple Facebook Reels URLs. **Does this Actor download and store the Reel files?** The Actor's primary output is structured dataset data and media URLs. It does not provide a downloaded media-file archive as its primary result. **Does it return separate video and audio URLs?** When separate video-only and audio-only streams are available, the corresponding URL fields can contain different media URLs. Otherwise, a combined format can be used as a fallback. **What metadata can I receive?** Possible successful results include the Reel URL, title, duration, description, thumbnail URL, media URLs, selected format information, and additional source information. **What happens when one Reel fails?** The Actor can continue processing other supplied URLs while writing an error record for the failed URL. **Why is a result field `null`?** A field may be unavailable in the information returned for a particular Reel. Review the full record before treating a missing value as a processing failure. **Is this Facebook Reels Downloader suitable for automation?** Yes, its URL-based input and structured Apify dataset output make it suitable for repeatable workflows where users already have the Reel URLs they want to process. **Should I test with a small number of URLs first?** Yes. A small test run makes it easier to verify your input structure and confirm that the returned fields match your intended workflow. ### NLP Keywords - Facebook Reels - Facebook Reel downloader - Facebook video extraction - Facebook audio extraction - Reel metadata - Reel video URL - Reel audio URL - Facebook media URL - Reel thumbnail - Reel title - Reel description - Reel duration - Facebook content data - structured Reel data - Reel format metadata - Facebook dataset - social media data extraction - Reel URL processing - media metadata extraction - Facebook Reel research ### Related Keywords - Facebook Reels downloader - download Facebook Reel video URL - download Facebook Reel audio URL - Facebook Reel metadata scraper - Facebook Reel URL extractor - Facebook video URL extractor - Facebook audio URL extractor - Facebook Reel data scraper - Facebook Reels data extraction - extract Facebook Reel information - extract Facebook Reel media links - Facebook Reel structured data - Facebook Reel thumbnail extractor - Facebook Reel title extractor - Facebook Reel description extractor - Facebook Reel duration extractor - Facebook Reel batch URL processing - Facebook Reel dataset generator - automate Facebook Reel data collection - Facebook Reel media metadata ### Final Overview Facebook Reels Downloader Audio or Video - Separate provides a focused way to process one or multiple Facebook Reel URLs and collect structured metadata plus available video and audio media URLs. Its output is designed around practical dataset use: each successful record can contain Reel information, thumbnail data, media URLs, selected format details, and source metadata. When processing fails for an individual URL, the result can identify the affected input through an error field. For best results, use valid Facebook Reel URLs, begin with a small test batch, inspect the dataset, and verify that the available fields meet the requirements of your workflow. **Contact me:** # Actor input Schema ## `startUrls` (type: `array`): Provide one or multiple Facebook Reels URLs ## Actor input object example ```json { "startUrls": [ { "url": "https://www.facebook.com/reel/1289152909325322" }, { "url": "https://www.facebook.com/reel/1606805090910208" }, { "url": "https://www.facebook.com/share/r/1GyTpE9i72/" } ] } ``` # Actor output Schema ## `dataset` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "startUrls": [ { "url": "https://www.facebook.com/reel/1289152909325322" }, { "url": "https://www.facebook.com/reel/1606805090910208" }, { "url": "https://www.facebook.com/share/r/1GyTpE9i72/" } ] }; // Run the Actor and wait for it to finish const run = await client.actor("alpha-scraper/facebook-reels-downloader-audio-or-video-separate").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "startUrls": [ { "url": "https://www.facebook.com/reel/1289152909325322" }, { "url": "https://www.facebook.com/reel/1606805090910208" }, { "url": "https://www.facebook.com/share/r/1GyTpE9i72/" }, ] } # Run the Actor and wait for it to finish run = client.actor("alpha-scraper/facebook-reels-downloader-audio-or-video-separate").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "startUrls": [ { "url": "https://www.facebook.com/reel/1289152909325322" }, { "url": "https://www.facebook.com/reel/1606805090910208" }, { "url": "https://www.facebook.com/share/r/1GyTpE9i72/" } ] }' | apify call alpha-scraper/facebook-reels-downloader-audio-or-video-separate --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,alpha-scraper/facebook-reels-downloader-audio-or-video-separate" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/nuvIRaMeRIzz3cfxK/builds/3B4BrsEGsdCNu7XvV/openapi.json