Best Video Downloader

Disclosure: Apify links in this README may include the fpr=aiagentapi referral parameter. If you sign up through one of these links, TrueFetch may receive a referral benefit at no additional cost to you.

Best Video Downloader turns one supported public video page into structured metadata and, when requested and available, a stored video file that you can use in an Apify workflow.

• The public input schema has three fields, with only video_url required and four explicit quality choices.
• The Dataset schema exposes 26 named fields covering identity, creator, engagement, media properties, comments, and the stored file URL.
• The Actor is addressable as truefetch/best-video-downloader and by the stable Actor ID ceeA8aQjRcp3E6cNx.
• On July 21, 2026, the public Store page displayed a 5.0 rating from 3 ratings, 213 total users, and 17 monthly active users; these figures are a dated snapshot and can change.

Run a one-result test

View API

Smallest-test risk note: start with one public URL, choose metadata, and leave max_comments unset. Source access and field availability vary, and the current billing configuration can charge the metadata event plus metered Actor usage.

What does Best Video Downloader do?

Best Video Downloader processes a single public video-page URL. It returns a normalized Dataset item with the values the source exposes, such as the video title, creator, publication time, duration, thumbnail, engagement counts, dimensions, tags, and categories. If you choose a download quality instead of metadata-only mode, the result can also contain a URL for the video file stored with the run.

The Actor is useful when your next step needs structured records rather than a page you must inspect manually. One run can feed an archive, research table, review queue, or application through Apify storage and APIs. Comment details are source-dependent: a source may expose a total count without returning individual comments.

“Supported” is deliberately not presented as a permanent site guarantee. Video sites change their pages and access rules, and generic or embedded players can behave differently from direct video pages. Use a one-URL test before scheduling repeated work or building a larger dependency on a particular source.

How do I run Best Video Downloader?

Open the Actor input page, paste one public video page into Video URL, and choose how much media you need. For the smallest evaluation, use metadata; this skips the video-file download while still producing the available Dataset fields. Leave Max Comments unset unless individual comment details matter to your use case.

For the shared example in this README, use:

{
  "video_url": "https://www.tiktok.com/@claude/video/7602306547670175006",
  "video_quality": "metadata"
}

Run the Actor and open Results after completion. Check the Dataset item rather than assuming every field is populated. If the metadata result fits your workflow, rerun with low, medium, or high as a quality preference. The selected label is a preference, not a promise that the source publishes that exact resolution; the available source formats determine the final media.

Use only URLs and media you are authorized to access and process. This Actor does not turn private, removed, region-restricted, or otherwise unavailable content into public content.

What data does Best Video Downloader return?

The Actor writes one normalized item for the processed URL. Source values that are unavailable can remain empty.

Data group	Dataset fields
Processing context	processor, processed_at
Video identity	id, platform, title, description, thumbnail
Creator	author, author_id, author_url
Publication and classification	published_at, categories, tags
Engagement	view_count, like_count, shares_count, dislike_count, comment_count
Media properties	duration, width, height, fps, audio_title, audio_artist
Optional details and file	comments, video

An abbreviated illustrative item for the same TikTok scenario looks like this:

{
  "id": "7602306547670175006",
  "platform": "TikTok",
  "title": "Example video title",
  "author": "claude",
  "thumbnail": "https://example.com/source-thumbnail.jpg",
  "view_count": 12500,
  "comments": null,
  "video": null
}

This example shows field shape, not a live response snapshot. Counts, URLs, titles, and availability can change at the source. In metadata-only mode, video is expected to be empty. When comments are requested and returned, each comment can include author, text, like_count, and published_at.

What inputs can I configure?

The effective input schema exposes the following fields in this order:

Input	Required	Type	Accepted values and effect
video_url	Yes	String	One public video page URL to process.
video_quality	No	String	high, medium, low, or metadata. The first three request a stored video; metadata skips it.
max_comments	No	Integer	From 0 to 10,000. It limits requested comment details where the source exposes them; 0 skips them.

Optional inputs have no schema prefill, so an omitted value remains genuinely omitted. That distinction matters in automation: send only the controls you intend to use. A large max_comments value is not evidence that a source has that many accessible comments, and it may increase processing work without increasing the returned count.

What platforms and markets does Best Video Downloader cover?

This is a general video-page Actor rather than a country, language, or marketplace-specific scraper. It is designed for supported public video URLs across a broad set of video and social sites, including pages handled through embedded or generic video extraction when available. Coverage is URL-driven; there is no market, country, language, date, or account filter in the public input.

The most reliable assessment is a representative public URL test. Historical coverage does not ensure that every page type, live stream, private post, age-gated item, or regional variant works today.

For platform-specific workflows, use a dedicated TrueFetch Actor when one exists. Those Actors make the supported scenario clearer and reduce ambiguity during integration testing.

Why use Best Video Downloader?

The main benefit is one normalized contract for a mixed collection of video URLs. Your downstream process can read the same 26 Dataset fields instead of maintaining a separate response shape for each source. Apify then provides run history, Dataset access, Key-Value Store links, scheduling, webhooks, API clients, and integration surfaces around that result.

Metadata-only mode is useful for triage: inspect identity, creator, engagement, and media properties before deciding whether you need the file. Quality preferences let you request media without pretending that every source offers the same formats. Nullable fields make partial source data explicit instead of filling gaps with invented values.

Who is Best Video Downloader for?

Developers and data teams can use it to turn a submitted video URL into a predictable record. Researchers can collect available public metadata for a documented sample. Content operations teams can create review queues with thumbnails, creators, timestamps, and engagement fields. Archivists can preserve authorized public media together with its source context. AI workflows can retrieve structured inputs before a separate transcription, classification, or summarization step.

It is not the right choice for account login automation, private-content access, legal-rights determination, search across an entire platform, or guaranteed archival preservation. It also does not replace a platform-specific Actor when you need platform-only filters or fields that are absent from this generic schema.

How can I use Best Video Downloader through the API or MCP?

Use Actor ID ceeA8aQjRcp3E6cNx or Actor reference truefetch/best-video-downloader. The live API page provides generated examples for available clients and the OpenAPI definition.

The following HTTP request starts the shared metadata-only scenario. Keep the token in an environment variable or secret manager.

curl -X POST "https://api.apify.com/v2/acts/truefetch~best-video-downloader/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"video_url":"https://www.tiktok.com/@claude/video/7602306547670175006","video_quality":"metadata"}'

For MCP, Apify currently recommends its hosted Streamable HTTP endpoint. A minimal bearer-token client configuration is:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=truefetch/best-video-downloader",
      "headers": {
        "Authorization": "Bearer <APIFY_TOKEN>"
      }
    }
  }
}

After connecting, ask the client to run truefetch/best-video-downloader with the same JSON input shown above. Running Actors and reading their storage require authentication. See the official Apify MCP documentation for OAuth, token, tool-selection, and client-specific setup.

How much does Best Video Downloader cost?

The checked-in metadata defines pay-per-event billing. The table below is the single pricing reference for the current configuration; verify the live Store price before production use because publication settings can change.

Billed event	Unit	Current price
actor_usage	Metered Actor usage event	$0.00001
metadata	One processed video without a file download	$0.05
download	One processed video with file download and storage	$0.25

For the smallest useful run in this README—one URL with video_quality: "metadata"—the value event is $0.05, plus any actor_usage units shown by the current billing setup. A download run uses the $0.25 event instead of the metadata event. Your Apify account may also show platform-related costs according to the Actor’s live pricing setup and your plan, so use the Console cost estimate and run detail as the final billing record.

The current local pricing contract is flat rather than tiered. No FREE, BRONZE, SILVER, or GOLD discount amounts are present in the effective metadata, so this README does not invent them.

How does Best Video Downloader compare with alternatives?

Option	Best fit	Main trade-off
Best Video Downloader	Mixed supported video URLs that need one normalized record and optional file	Generic coverage means source-specific fields and comment availability vary.
Dedicated TrueFetch downloader	Repeated work on one named platform	Narrower scope, but clearer platform semantics and testing.
Manual browser download	Occasional personal inspection	Difficult to automate, normalize, audit, or connect to Dataset workflows.
Direct platform API	A platform with an API that grants your required access	Requires separate credentials, permissions, quotas, response handling, and integrations per platform.

Choose this Actor when a shared response shape is more valuable than platform-specific controls. Choose a dedicated Actor or official platform API when your acceptance criteria depend on one platform’s exact fields, authentication model, or policy-controlled features.

What are the limits and troubleshooting steps?

The Actor accepts one URL per run; it is not a batch list input. It does not search for videos. Private, deleted, login-gated, age-gated, live, region-restricted, or source-blocked pages may fail or return partial data. Fields are nullable because different sources publish different values. Comment totals and individual comment details are separate concepts, and requesting comments does not guarantee that the source returns them.

If a run has no useful result, first verify the exact URL in a normal browser and confirm it points to one public video page. Retry with video_quality: "metadata" and no max_comments to isolate basic page processing. If metadata works, add the media request, then add comments last. If a requested quality is unavailable, the Actor may use another available format rather than enforcing a strict resolution ceiling.

When a file URL is empty, confirm that you did not select metadata-only mode. Treat empty engagement fields as unavailable rather than zero, and monitor scheduled runs because source behavior can change.

Frequently asked questions

Can I submit multiple URLs in one run?

No. The public schema accepts one video_url. Start separate runs or orchestrate them externally if you have a list.

Does high guarantee 4K?

No. It requests the best available media preference. Final resolution depends on formats available for that exact page.

Are comments supported on every platform?

No. Comment details are source-dependent. A page may provide comment_count while comments remains empty.

Does metadata-only mode return a video file?

No. It is intended to return available metadata without the stored video URL.

Why are some fields null?

Sources expose different fields, and values can be unavailable. Null is preferable to fabricating a value or treating an unavailable count as zero.

Will the same URL always return identical data?

No. Titles, counts, availability, and media formats can change at the source. Repeated submissions also create separate runs and results.

Can I schedule the Actor?

Yes, Apify can schedule Actor runs, but this input processes one fixed URL per run. Decide whether repeating that URL matches your use case and cost expectations.

How should I verify billing?

Use the live Store pricing and the completed run’s charge details. The checked-in prices documented here are a configuration snapshot, not a guarantee against later publication changes.

Related TrueFetch Actors

• YouTube Video Downloader is the clearer choice when every input is a YouTube video and you want platform-specific documentation.
• TikTok Video Downloader narrows testing and support expectations to TikTok video pages.
• Video To Text is the next step when the workflow needs speech converted to text rather than only the media and page metadata.

Use Best Video Downloader when one workflow must accept more than one supported source; use the dedicated option when predictability for a single named platform matters more.

Support and last updated

Documentation and public-surface evidence in this README were checked on July 21, 2026. The online Store copy and statistics are volatile and may lag or change independently of this repository.

• Store page
• API and integration examples
• Actor issues
• TrueFetch community
• Direct support

For a reproducible support request, include the public URL or a safe equivalent, input JSON with secrets removed, run ID, expected field or file, and the observed result.

Run a one-result test

View API