All Video Scraper avatar

All Video Scraper

Pricing

Pay per event

Go to Apify Store
All Video Scraper

All Video Scraper

Universal video downloader API for YouTube, TikTok, Instagram, X, Twitch and 1000+ more sources. Pass one video URL and choose 4K, 720p, 480p, or metadata-only. Returns 39 normalized fields per video, including views, likes, comments, author, duration, subtitles and chapters, plus a stored file URL.

Pricing

Pay per event

Rating

4.6

(6)

Developer

AgentX

AgentX

Maintained by Community

Actor stats

10

Bookmarked

233

Total users

15

Monthly active users

18 hours ago

Last modified

Share

All Video Scraper is a video downloader api that turns one public video link into a 43-field record — title, creator, engagement counts, media properties, subtitles and chapters — and optionally stores the video file itself.

Apify Users Apify Runs $0.09 per record comments%20on%20request API + MCP ready

  • One link in, 43 fields out. Identity, creator, engagement, media properties, subtitles and chapters arrive as typed values rather than as a page to parse.
  • Metadata or file, priced apart. Reading a record and storing a video cost very different amounts, so they bill as different events instead of one blended price.
  • No any supported source key, no quota. One endpoint across every source in this family and around a thousand more. The row shape does not change with the source, so a mixed queue of URLs parses with one reader.
  • Verified August 9, 2026. A metadata run finished in 2.1 seconds inside the Actor's own image at its published memory.

The smallest useful run reads one record: one Actor Start plus one Metadata event, $0.10 on the FREE tier.

Why Choose All Video Scraper

Because the answer arrives already structured, already typed, and identical to every other edition in the family.

One row shape, whatever the source. The 43 fields are defined once and shared, so code written for this edition reads every sibling without a branch.

Honest inputs. This edition offers 3 inputs — video_url, video_quality, max_comments — and no others. A control that any supported source cannot honour is left out rather than shipped as decoration.

Costs that match the work. A metadata read is $0.09; storing the file is $0.28. Nothing is averaged across the two.

Quick Start Guide

Three steps, and the input arrives prefilled with a working example.

Open the Actor input and put a video URL from any supported source in video_url.

Step 2: Choose what you want back

Leave video_quality on metadata for the record alone, or pick low, medium or high to also store the file.

Step 3: Run it and read the Dataset

Click Start. One run produces one row in the default Dataset, and the stored file URL lands in the video field when you asked for a download.

Input Parameters

This edition takes 3 inputs, of which one is required.

ParameterTypeRequiredDescription
video_urlstringYesThe any supported source link to read. Accepts a video URL from any supported source.
video_qualitystringNometadata reads the record only. low, medium and high also store the file at 480p, 720p and up to 4K.
max_commentsintegerNoHow many comment bodies to request. 0 skips them.
{
"video_url": "https://www.youtube.com/watch?v=aqz-KE-bpKQ",
"video_quality": "metadata",
"max_comments": 0
}

Output Data Schema

One Dataset row per run, with 43 fields in a fixed set.

GroupFields
Identityid, source_url, platform, title, description, duration, published_at
Creatorauthor, author_id, author_url, followers, is_verified
Engagementview_count, like_count, dislike_count, comment_count, shares_count, saves_count
Mediawidth, height, fps, video_codec, audio_codec, bitrate, dynamic_range, file_ext, file_size
Classificationcategories, tags, language, media_type, live_status, availability, age_limit
Extrasthumbnail, subtitles, chapters, comments, audio_title, audio_artist, video
Provenanceprocessor, processed_at

A value the source does not publish stays null rather than being filled in, and video is empty on a metadata run.

Integration Examples

The Actor is callable from the REST API, the Apify clients, and any MCP-aware assistant.

curl -X POST 'https://api.apify.com/v2/acts/etzrjsBIFSOb19k5E/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN' \
-H 'Content-Type: application/json' \
-d '{"video_url": "https://www.youtube.com/watch?v=aqz-KE-bpKQ", "video_quality": "metadata"}'

The Actor ID etzrjsBIFSOb19k5E is stable; the agentx/all-video-scraper name also resolves.

Pricing

Billing is per event, and the two events are priced apart because they cost differently to serve.

EventFREEWhat triggers it
Actor Start$0.01Once per run
Metadata$0.09One record read, no file transferred
Download$0.28One record plus the stored video file

Paid tiers discount the record events: Bronze 10%, Silver 20%, Gold and above 25%.

Use Cases

The common thread is needing the record as data rather than as a page.

  • Archiving. Keep a durable copy of any supported source material with its metadata attached, not just the file.
  • Research datasets. Engagement counts and publication times across many links, in one shape.
  • Content pipelines. Feed a transcription, translation or repurposing step that needs the file and its properties.
  • Monitoring. Track how a known item's counts move over time.

Alternatives

Which tool fits depends on whether you have one link or a queue of them.

  • All Video Scraper — the same contract across every supported source, for a mixed queue.
  • A browser extension — fine for one file by hand; it produces no structured record and cannot be scheduled.
  • any supported source's own API, where one exists — contractual and quota-limited, a different commercial model rather than a worse one.

Limits and Troubleshooting

Most failures come down to what the link points at.

  • Private, deleted or region-locked items cannot be read and end the run with a message rather than an empty row.
  • Unsupported sources are refused rather than returning an empty row.
  • Live items have no finished recording to read until they end.
  • Empty engagement counters usually mean the source did not publish them, which is why the contract uses null rather than zero.

Trust and Reliability

Every claim on this page is checkable against the Actor's own files or a run you can repeat.

The 43 fields are defined in the Actor's dataset_schema.json. The prices are in its pricing configuration and shown on the pricing tab. The 2.1-second figure is a metadata run in the Actor's published image at 256 MB, measured August 9, 2026. Run history, logs and Dataset exports for your own runs live in the Apify Console.

This Actor is not affiliated with any supported source, and reads only what a public visitor can already see.

You are responsible for how you use what it returns. Copyright, database rights and the source's own terms continue to apply to downloaded media, and personal data in creator fields and comments falls under the privacy law of your jurisdiction. Material behind a login, a paywall or a privacy setting is out of scope and the Actor makes no attempt to reach it.

Frequently Asked Questions

Do I need a any supported source account or API key?

No. The Actor reads the same public page a browser does, so there is no any supported source login, no OAuth step and no daily quota to plan around. You need an Apify token to call the Actor itself.

What does one run cost?

A metadata run bills one Actor Start plus one Metadata event — $0.10 on the FREE tier. Choosing a download quality bills the Download event at $0.28 instead, because transferring and storing a file costs far more than reading a page.

How fast is a single run?

About 2.1 seconds for a metadata read, measured in the Actor's own container at its published 256 MB. A download takes as long as the transfer; a 4K file measured just under two minutes.

The run ends with a message saying the video could not be retrieved, and no row is pushed. You are not billed a record event for a row that does not exist.

Which sources are supported?

Every source in the AgentX and TrueFetch video families plus roughly a thousand more, all through the same row shape.

Does it return comments?

Yes. Set max_comments to the number of comment bodies you want; 0 skips them and keeps the run to a metadata read.

Is the field set the same across the family?

Yes. All 43 fields come from one shared contract, so a reader written against one edition parses every other one without a branch.

AgentX publishes the following Actors.

Business and Market Intelligence

Jobs and Hiring

Social Media

Video, Transcripts and Downloads

E-Commerce and Retail

Classifieds and Automotive

Real Estate

Support and Community

Ask about fields, runs or billing in the AgentX community on Telegram; for a reproducible bug, open an Issue with the run ID and the exact input.

AgentX is an Arcyton brand — arcyton.com.

Last Updated: August 9, 2026