YouTube Download · from Actor runs to bulk delivery
Apify Alternative for YouTube Download
Move the downloads. Keep your workflow.
Upload a file of video IDs, choose your output and receive media in your bucket. Compare the download actor you use, then move one queue through the FlashData console.
Read as Markdown · Reviewed 2026-11-10
01 · Focus on delivery cost and control
Feature-by-feature comparison
Compare the Streamers and epctex download actors across pricing, output controls and storage workflows.
| Feature | FlashData | Apify download actors |
|---|---|---|
| Cost and access | ||
| Lowest self-service per-GB rate | $0.04/GBBusiness · $1,999.00 / month | Streamers: $2.50/GBBusiness · $999/month; epctex bills seconds instead |
| Entry paid download rate | $0.10/GBPay as you go; no monthly fee | Streamers: $5/GB on Starter$19/month; epctex: $0.15–$1.20 per 1,000 seconds |
| Paid usage without a monthly subscription | YesCredit top-ups from $10 | Free budget, then a paid planStandard account plans start at $19/month, including $19 usage |
| Starting allowance | Up to 20 GBEligible verified signup; shared initial balance | $5 shared Free-plan budgetepctex also limits Free accounts to 2 runs/month |
| One billing unit across output choices | Uploaded bytesVideo, audio and clips use the plan’s delivery rate | Depends on the ActorStreamers: downloaded MB; epctex: seconds at the selected resolution |
| Video and audio output | ||
| Video quality | Up to 8K4320p; exact, minimum or maximum resolution | Up to 4K in both actors2160p is the highest input-schema option |
| Choose the video container | YesMP4 · WebM · MKV | Streamers: multiple formatsIncludes MP4, WebM, MKV, AVI and MOV; epctex has no selector listed |
| Audio-only output | YesM4A · MP3 · Opus | Streamers: audio formatsIncludes MP3, M4A, Opus and FLAC; epctex lists video quality only |
| Frame rate and audio bitrate | YesFPS filters; audio quality from 128 to 320 kbps | Not listedNeither input schema exposes FPS or bitrate fields |
| Custom format selection | Yesyt-dlp format selectorSelect available streams with yt_dlp_format | Not listedNeither input schema exposes a raw format selector |
| Download a video or audio clip | YesStart and end timestamps | Not listedNeither input schema lists clip boundaries |
| Save metadata alongside the media | YesOptional JSON sidecar; metadata bytes not billed | Actor-specific result recordsNo metadata-sidecar option in either reviewed input schema |
| YouTube captions and transcripts | YesSeparate YouTube Data requests; same balance | Streamers: subtitles + transcriptionYouTube subtitles or separately priced AI transcription |
| Storage and production workflows | ||
| Upload an ID file in the console | YesUTF-8 .txt, up to 2 GiB; progress, pause and resume | Actor input form or APIURL / ID arrays with the chosen Actor’s schema |
| Cloud-storage destinations | S3 + S3-compatible, GCS, AzureAlso OSS, COS, BOS and TOS | Both actors support cloud deliveryS3, GCS and Azure; epctex also lists DigitalOcean |
| One result workflow for media and video datasets | Bulk ID, manifest and result partsUse the same Bulk Jobs workspace for Download and YouTube Data | Run, dataset and storage recordsChoose each Actor’s schema and adapt the result consumer |
| Delivery record for file verification | file_url + file_size + md5Download records in Bulk result parts | Actor-specific dataset outputepctex publishes URL, status, duration and cost |
| Keep your existing scheduler | YesYour runner submits jobs; a webhook signals completion | YesApify has hosted schedules and webhooks |
| Agent tools and recurring access | CLI, SDKs, MCP and skillsOwner-approved Download permission and revocable credentials | Apify MCP, CLI and API clientsOAuth or API token; agent discovers and runs the chosen Actor |
02 · Start with your actual Actor
A download price needs a billing unit.
These are two specific download actors, not a platform-wide Apify rate. Both use pay-per-event pricing. The Streamers GB figures normalize 1,000 billed MB to 1 GB; epctex needs duration and resolution instead of file size.
| Download actor | What is billed | Published rates | Output and options |
|---|---|---|---|
| streamers/youtube-video-downloader | Downloaded MB; plan discounts apply | $6 / GB on Free, $5 on Starter, $4 on Scale, $2.50 on Business | Video or audio; cloud delivery or temporary Apify storage. AI transcription is a separately priced add-on. |
| epctex/youtube-video-downloader | Full video duration at the selected resolution | $0.15–$1.20 per 1,000 seconds, from 360p to 4K | Apify storage or your cloud. Duration is charged upfront. Free accounts: up to 2 runs/month. |
Apify plan fees and Streamers rates
| Apify plan | Monthly fee | Included usage | Streamers / GB |
|---|---|---|---|
| Free | $0.00 | $5.00 | $6.00 |
| Starter | $19.00 | $19.00 | $5.00 |
| Scale | $199.00 | $199.00 | $4.00 |
| Business | $999.00 | $999.00 | $2.50 |
Published standard monthly plans. The included usage is a dollar budget, not a video allowance. Enterprise tiers are excluded.
epctex rates by resolution
| epctex resolution | Per 1,000 video seconds | 10-minute video |
|---|---|---|
| 360p | $0.15 | $0.09 |
| 480p | $0.25 | $0.15 |
| 720p | $0.45 | $0.27 |
| 1080p | $0.75 | $0.45 |
| 1440p | $1.00 | $0.60 |
| 2160p / 4K | $1.20 | $0.72 |
The same event rates apply across these standard plans. A 10-minute 1080p video incurs $0.45 in download events; its size in GB must be measured separately.
03 · Choose both plans and your Actor
Compare the queue you need to deliver.
Use GB for media volume. Add duration and resolution when comparing epctex.
streamers/youtube-video-downloader
Compare equal media volume: FlashData settles uploaded bytes; Streamers charges downloaded MB. 1 GB = 1,000 MB here.
FlashData · Pay As You Go
$0.10per GB of delivered media
- Monthly plan fee
- $0.00
- Included shared value
- $0.00
- Download equivalent
- 0 GB
- Download usage
- $10.00
- Beyond included value
- $10.00
- Fee + usage funding
- $10.00
- Minimum purchase
- $10.00
Top-ups start at $10 and can leave a balance for later. Included value is shared across FlashData products.
Apify · Starter · Streamers
$5.00per 1,000 downloaded MB (1 GB)
- Monthly plan fee
- $19.00
- Included platform usage
- $19.00
- Download event usage
- $500.00
- Beyond included usage
- $481.00
- Fee + usage funding
- $500.00
The included budget is shared with other Apify work. Optional add-ons and post-run platform usage are separate.
How this estimate works
USD, monthly billing. FlashData usage = delivered GB × its plan rate. Streamers event usage = billed MB × its tier rate (1,000 MB per displayed GB). epctex event usage = total minutes × 60 × the resolution’s per-second rate. Monthly funding = plan fee + usage beyond included value; the included value is subtracted once and assumed available for this workload. Apify Free stops at its $5 budget, and epctex Free also limits accounts to 2 runs/month. FlashData top-ups start at $10; minimum purchase assumes no existing balance. The comparison models download events, with no extra compute or proxy surcharge added to these actors. Optional transcription, post-run platform operations, destination storage and any custom orchestration are separate.
All FlashData Download plans
| FlashData plan | Per GB | Monthly fee | Included shared value | Download equivalent |
|---|---|---|---|---|
| Pay As You Go | $0.10 | $0.00 | $0.00 | 0 GB |
| Micro | $0.08 | $49.00 | $50.00 | 625 GB |
| Starter | $0.07 | $199.00 | $200.00 | 2,857.14 GB |
| Pro | $0.06 | $499.00 | $500.00 | 8,333.33 GB |
| Scale | $0.05 | $999.00 | $1,000.00 | 20,000 GB |
| Business | $0.04 | $1,999.00 | $2,000.00 | 50,000 GB |
04 · Your first bulk delivery
Move one ID file through the console.
Sign in with available credits and a writable storage destination. Prepare your queue:
- Take the YouTube IDs from your Actor input or exported dataset. Include only videos still needing delivery; keep files you already downloaded.
- If your current media is in an Apify key-value store, copy any files you need to retain before its retention expires. A dataset export contains records, not the video files themselves.
- Group IDs by output and storage settings. Start a small file under a fresh bucket prefix, then compare the delivered files and records before switching the remaining queue.
1Save your video IDs
Save video-ids.txt on your computer as UTF-8 text, one YouTube video ID per line. Replace these sample IDs with your own list; use IDs, not full URLs or a header row.
jNQXAC9IVRw
dQw4w9WgXcQ
Remove duplicates and start with a few videos. The console accepts .txt files up to 2 GiB.
2Choose your output and storage
In Bulk Jobs, click New bulk job. Select YouTube Download as the Source and attach video-ids.txt under YouTube IDs file.
Output: For a first run, choose Video + audio, mp4 and a 720p ceiling. Use Advanced download options for clips or Upload metadata JSON.
Storage: Choose your Storage type, enter the bucket or container and upload credentials, then set an Object prefix such as migration/downloads/test-01. Credentials must allow writes to that destination.
One set of output settings applies to the whole file. Use separate jobs for different formats or quality settings.
3Create the job and follow progress
Click Create and upload. The console uploads the file, starts processing and opens the job page. Progress refreshes automatically; check Accepted, Completed, Failed and Invalid counts.
Bookmark this job page. Pause stops new submissions; accepted work can still finish. Resume continues the same job.
4Open the files in your storage
Find the delivered video or audio files under your chosen storage prefix, with metadata JSON if enabled. Check the Failed and Invalid counts before treating the whole list as complete.
For delivery records, click Download manifest, then use its part numbers with Download result part. Retrieve these records within 24 hours of completion; media follows your own storage retention policy.
Eligible verified signups can receive an initial shared balance worth up to 20 GB of downloads. Temporary-agent trials do not include Download; an agent needs owner-approved access.
05 · Carry over the parts your app reads
Keep discovery, schedules and consumers connected.
| Your Apify workflow | FlashData equivalent | What to carry over |
|---|---|---|
| Actor input: videos[], startUrls[] or videoIds[] | YouTube IDs file | Extract individual video IDs into UTF-8 text. Actor JSON, playlist URLs and dataset rows are not the upload format. |
| Saved Task with quality and storage options | Bulk job output settings + storage destination | Select the format and quality ceiling; enter storage credentials in the console. Actor input field names do not transfer automatically. |
| Run ID + defaultDatasetId | Bulk ID + manifest + result parts | Record the new job ID. Adapt your consumer to per-item results and stored object locations; old dataset IDs remain on Apify. |
| Temporary media URLs from a key-value store | Media objects in your own bucket | Use your bucket’s access and retention rules. The result manifest is a delivery record, not a ZIP containing the media. |
| Schedule + run-completed webhook | Your scheduler + Bulk completion webhook | Carry over cadence, timezone and the consumer. Poll the saved Bulk ID instead of resubmitting the input file. |
| Run spending cap or platform usage limit | Application budget checks + shared account balance | Existing Apify limits are not imported. Use a small first job and account checks; an owner API key has no separate spending cap. |
Automate after the first console job
Keep Apify for discovery or scheduling if it already serves your workflow. A custom Actor can submit a FlashData Bulk job and write delivery records back to an Apify dataset; its own platform usage remains separate. For direct automation, use your app, CI or agent host with the Bulk API and a saved owner credential.
Save the Bulk ID and delivery records. Retry only reviewed failures; reconnect your downstream consumer before retiring the old download task.
06 · Before switching the queue
Questions from Apify users
Why are there two different Apify prices?
Each Actor defines its chargeable events. Streamers meters downloaded MB; epctex meters video seconds by resolution. Choose the actor you actually use in the calculator. There is no reliable conversion from minutes to GB without the size of the same output files.
Can I keep my existing cloud bucket?
Both compared actors support S3, GCS and Azure delivery, which FlashData also supports. Select your destination in Bulk Jobs, enter its upload credentials and choose a fresh object prefix. FlashData also supports S3-compatible storage, OSS, COS, BOS and TOS.
Can I retain Apify schedules and dataset consumers?
Yes, through your own integration. Keep discovery or a custom orchestration Actor, submit FlashData jobs, then write their delivery records to the dataset your consumer reads. There is no automatic transfer of Actor Tasks, run IDs or schedules.
Does the monthly subscription add to every event charge?
The included usage budget pays for events first. Only usage beyond that budget is added to the monthly plan fee. The calculator assumes that budget is available for these downloads; other workloads can consume it.
Can an AI agent start with a temporary trial?
YouTube Download requires owner-approved access and available account credits. A temporary agent trial does not include Download. After approval, the agent can reuse its stored credential, save each Bulk ID and check progress without asking you to paste a key into chat.
Does Download include generated transcripts?
FlashData Download delivers video or audio, with optional metadata JSON. Retrieve existing YouTube captions through YouTube Data, and keep speech-to-text as a separate processing step. The Streamers AI transcription add-on is outside this download cost comparison.
Start with the next delivery
Your IDs. Your output. Your bucket.
Run a small Bulk Download in the console.