Facebook AI Transcript Extractor avatar

Facebook AI Transcript Extractor

Pricing

from $6.00 / 1,000 video processeds

Go to Apify Store
Facebook AI Transcript Extractor

Facebook AI Transcript Extractor

Transcribe public Facebook videos and Reels into timestamped text, SRT, and WebVTT subtitles.

Pricing

from $6.00 / 1,000 video processeds

Rating

0.0

(0)

Developer

Fetch Cat

Fetch Cat

Maintained by Community

Actor stats

0

Bookmarked

3

Total users

1

Monthly active users

24 days ago

Last modified

Categories

Features

Limited permissions

Share

Turn anonymously accessible Facebook videos and Reels into searchable transcripts, timestamped segments, SRT subtitles, and WebVTT captions. Use this Facebook AI transcript extractor for research, accessibility drafts, content analysis, or downstream AI workflows. Private and login-gated media are not supported.

Quick start

  1. Paste a public Facebook Reel or video URL into Facebook video or Reel URLs.
  2. Start with one short video. Leave language empty unless you know the source language.
  3. Run the Actor, then open the dataset to export JSON, CSV, or Excel. Save srtSubtitles or vttSubtitles as a subtitle file.

Use the full facebook.com/reel/ID or facebook.com/PAGE/videos/ID URL, not a fb.watch, share, or Watch-page link.

Example input:

{
"videoUrls": [
"https://www.facebook.com/cnn/videos/10155529876156509/"
],
"maxVideoDurationSeconds": 900,
"language": "en"
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

What you get

Each saved transcript is one dataset row linking its source video to text, timestamped segments and subtitle documents. Available video and uploader metadata help you trace the result back to its source.

Who is it for?

  • Researchers and journalists who need searchable quotations and timestamps from public videos.
  • Accessibility teams preparing subtitle drafts for authorized content.
  • Content and social teams indexing spoken material across a small URL batch.
  • Developers and AI builders feeding structured transcripts into search, summarization, or retrieval pipelines.

Common workflows

  • Find a quotation in an interview. Transcribe one public video, search the text and use the segment timestamps to return to the recording. Check names, numbers and quotations against the original audio.
  • Prepare subtitle drafts. Process one public Reel or video and save its SRT or WebVTT output. Review the wording and timing before using the subtitles.
  • Index a small research batch. Start with two or three public video URLs and keep each transcript with its source link. Check RUN_SUMMARY for empty, failed or unfinished targets before treating the batch as complete.

Input settings

Setting / API keyTypeDescription
Facebook video or Reel URLs / videoUrlsarrayRequired: 1–20 public video URLs, as strings or { "url": "..." } objects.
Maximum video duration / maxVideoDurationSecondsinteger10–7200 seconds. Omitted input uses 900 seconds.
Language hint / languagestringOptional source language, such as en or es. Not a translation target. See field help for selection behavior.

Input recipes

  • One short Reel: submit one URL and set maxVideoDurationSeconds to 120.
  • Small research batch: submit up to 20 public URLs. Start small because long videos may leave later targets unfinished.
  • Known source language: set language to the spoken language, not the language you want to translate into.

Output data

Illustrative shape only. Transcript text and timing below are not a captured quotation. Optional metadata may be absent.

{
"status": "succeeded",
"sourceUrl": "https://www.facebook.com/cnn/videos/10155529876156509/",
"canonicalUrl": "https://www.facebook.com/cnn/videos/10155529876156509/",
"videoId": "10155529876156509",
"transcript": "Timestamped transcript text...",
"language": "en",
"segments": [{ "text": "Timestamped transcript text...", "startSeconds": 0, "endSeconds": 4.2 }],
"srtSubtitles": "1\n00:00:00,000 --> 00:00:04,200\nTimestamped transcript text...",
"vttSubtitles": "WEBVTT\n\n00:00:00.000 --> 00:00:04.200\nTimestamped transcript text..."
}

More output fields

Each successful video produces one dataset row.

FieldDescription
statusProcessing status.
sourceUrl, canonicalUrlSubmitted URL and the source's video-page URL when available.
videoId, videoTitle, descriptionPublic video identity and text metadata.
durationSecondsVideo duration.
uploaderName, uploaderId, publishedAtPublic uploader and publication metadata when available.
thumbnailUrlPublic preview image URL when available.
mediaFormatSelected public media format when available.
transcript, languageFull transcript and selected/requested language. May be unknown.
segmentsTimestamped objects with text, startSeconds, and endSeconds.
srtSubtitles, vttSubtitlesReady-to-save subtitle documents.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

The Actor uses pay per event: start once per run after input validation, and apify-default-dataset-item (Video processed) for each transcript saved to the dataset.

Failed targets do not produce a saved row or incur the per-transcript event. A run with no saved transcripts can still incur the start event.

See the live Pricing tab for current rates and plan-based volume discounts.

Tips for best results

  • Use direct public video or Reel URLs. Only public, directly addressable Facebook videos and Reels are supported. Login-only, deleted, private, geo-restricted, or rights-restricted media may fail.
  • Start with clear speech. Clear speech produces better results than music, overlapping speakers, or loud background noise. Speech recognition uses multilingual Whisper tiny with voice activity detection. Singing may be filtered out. An empty transcript does not prove that the video contains no audible words.
  • Check the batch summary. A batch preserves successful rows when another URL fails. RUN_SUMMARY and STATE in the key-value store describe failures, unfinished targets, and completed-empty results (empty count and per-input emptyResults reasons).
  • Avoid submitting the same URL twice. Repeated URLs are processed once, in input order. There is no search, sorting, speaker labeling, or translation setting.
  • Distinguish empty results from failures. Completed extraction with no usable speech or caption segments succeeds with an empty dataset. Empty targets produce no placeholder rows or per-video dataset charges. The run startup fee still applies. Parser, subprocess, deadline, billing, and essential storage failures are not completed-empty results. A batch with only processing failures fails. Do not treat every inaccessible URL as private or deleted.
  • Review the transcription. Timestamps and speech recognition are drafts: review important names, numbers, and quotations.

Limits and caveats

The duration setting accepts 10–7200 seconds (900 when omitted). The actual decoded audio is checked against that limit, with a small allowance for codec padding. Long recordings are processed in bounded windows. The returned timestamps still refer to the full recording. Caption responses larger than 2 MB fail clearly rather than being treated as empty transcripts.

The Actor stops admitting videos when your spending limit cannot cover another saved transcript. RUN_SUMMARY.stoppedReason is budget-limit, and pending lists unfinished URLs. A successful budget-limited run does not mean every requested video was transcribed.

Restarting the same run preserves its original processing allowance, reconciles already saved transcripts and resumes unfinished videos. It does not repeat the start fee or intentionally write the same video's transcript twice. Changing the input after processing has begun requires a new run.

Available records and fields depend on your input and the source. Review the returned data before using it in another system. A successful run does not guarantee that every requested record or optional field was available.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~facebook-ai-transcript-extractor/runs' \
-H "Authorization: Bearer $APIFY_TOKEN" \
-H 'Content-Type: application/json' \
--data @- <<'JSON'
{
"videoUrls": [
"https://www.facebook.com/cnn/videos/10155529876156509/"
],
"maxVideoDurationSeconds": 900,
"language": "en"
}
JSON

Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/facebook-ai-transcript-extractor').call({
"videoUrls": [
"https://www.facebook.com/cnn/videos/10155529876156509/"
],
"maxVideoDurationSeconds": 900,
"language": "en"
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient
client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/facebook-ai-transcript-extractor').call(run_input={'videoUrls': ['https://www.facebook.com/cnn/videos/10155529876156509/'], 'maxVideoDurationSeconds': 900, 'language': 'en'})
print(client.dataset(run['defaultDatasetId']).list_items().items)

MCP and AI agents

You can ask your AI assistant to collect data with Facebook AI Transcript Extractor and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Facebook AI Transcript Extractor. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com?tools=fetch_cat/facebook-ai-transcript-extractor"
}
}
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Facebook AI Transcript Extractor by Fetch Cat, or give it the identifier fetch_cat/facebook-ai-transcript-extractor.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

Give your assistant a public video URL or a short URL list with a request like one of these:

  • “Use Fetch Cat’s Facebook AI Transcript Extractor on this public video: https://www.facebook.com/cnn/videos/10155529876156509/. Process only this URL with a 900-second duration limit. Return the transcript and timestamped segments, and report if no transcript was saved.”
  • “Transcribe the one public Facebook Reel URL I provide with a 120-second duration limit. Return its source URL, transcript and SRT subtitles, and flag any processing failure.”
  • “Process up to three public Facebook video URLs I provide with a 900-second duration limit per video. Return the transcripts and WebVTT captions with their source URLs. Separate saved transcripts, completed-empty targets, failures and unfinished URLs.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Does it work without a Facebook login?

It processes public URLs that Facebook exposes anonymously. It does not bypass login, privacy, or access restrictions.

Can I export Facebook video transcripts as SRT or WebVTT?

Yes. Save the srtSubtitles or vttSubtitles field from each dataset item as an .srt or .vtt file.

Why did a public URL fail?

The media may be temporarily unavailable or restricted by location, rights, age, or Facebook delivery changes. Completed extraction with no usable speech succeeds without a transcript row. It is not a processing failure. Review the run log and RUN_SUMMARY.

Can I run Facebook video transcription through an API or MCP client?

Yes. Use the Apify API, official clients, webhooks, integrations, or the MCP endpoint above.

Is this an alternative to manual transcription?

It automates first-pass transcription for small URL batches. Review important names, numbers, and low-quality audio before publication or compliance use.

Continue a Facebook content workflow with:

  • Facebook Pages Scraper — Collect public Page profiles, available contact fields and optional visible post links to add source context to a transcript collection.
  • Facebook Ads Library Scraper — Collect public ad copy, advertiser details and available creative URLs by keyword, advertiser Page ID or Ads Library search URL.
  • Facebook Comments Scraper — Collect visible comment text, author names and available engagement details from known public post URLs.
  • Facebook Events Scraper — Collect public event dates, venues, hosts and available ticket links from event or organizer URLs.
  • Facebook Reels Scraper — Collect public Reel URLs, IDs, visible play counts and available owner metadata from Reels tabs, usernames or known Reel URLs.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, non-sensitive input JSON, expected output, actual output and one reproducible public video or Reel URL.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥