MEGA File Uploader & Downloader Bypass MEGA download limit and transfer quota with this Apify actor. Automate uploading and downloading MEGA.nz files and folders with ease. Ideal for automation workflows, daily backups, file delivery tasks, and sharing large files without hitting the dreaded "transfer quota exceeded" error. ## Features - ✅ Bypass MEGA download limit and transfer quota restrictions - ✅ Download files from MEGA.nz public links (no login required) - ✅ Upload files to MEGA.nz (requires MEGA login) - ✅ Create public shareable links for uploaded files - ✅ Supports batch processing of multiple MEGA URLs or local files - ✅ Support for file size limits during downloads - ✅ Automatic folder creation for uploads - ✅ Store results in Apify datasets and KV stores ## Why Use This? Are you tired of the "transfer quota exceeded MEGA" message? This tool is your solution to bypass MEGA transfer quota limits, automate MEGA file uploads/downloads, and avoid download restrictions. Whether you're looking for a MEGA downloader online or an automation tool to handle backups to MEGA.nz, this actor gets it done without manual intervention. ## Input Schema | Field | Type | Required | Description | | -------------------- | --------- | ------------------ | ---------------------------------------- | | action | string | ✅ | Either "upload" or "download" | | megaUrls | array | ✅ (for download) | Array of MEGA.nz URLs | | downloadAll | boolean | ❌ | Download entire folder | | downloadLimitMB | integer | ❌ | Skip files larger than this limit | | outputFolder | string | ❌ | KV store folder name | | email | string | ✅ (for upload) | MEGA account email | | password | string | ✅ (for upload) | MEGA account password | | filesToUpload | array | ✅ (for upload) | Array of local file paths | | uploadNames | array | ❌ | Rename files during upload | | uploadFolderName | string | ❌ | Create folder in MEGA | | createPublicLink | boolean | ❌ | Generate shareable links | ## Output Schema The actor returns an array of objects, with each object representing either a downloaded or uploaded file. The output format depends on the action: ### Download Results json [ { "fileName": "GTA-5-Characters-GTA-6.png", "fileSizeBytes": 3353675, "downloadUrl": "https://mega.nz/file/PR1wmDyI#z7twJZCOPKoxW0zsgRlS20mi53EzY7PvzQplwAPSKEE", "status": "downloaded", "localPath": "/usr/src/app/downloads/GTA-5-Characters-GTA-6.png", "kvStoreKey": "downloads-GTA-5-Characters-GTA-6.png", "apifyDownloadUrl": "https://api.apify.com/v2/key-value-stores/ajIIjbpkrcl3qdMBI/records/downloads-GTA-5-Characters-GTA-6.png" } ] ### Upload Results json [ { "fileName": "asda-leyton-mills.jpg", "originalPath": "https://dynamic-media-cdn.tripadvisor.com/media/photo-o/17/37/a9/8d/asda-leyton-mills.jpg", "status": "uploaded", "fileSize": 36315, "publicLink": "https://mega.nz/file/ABCDEF#key" } ] ### Field Descriptions #### Download Results - fileName: Name of the downloaded file - fileSizeBytes: Size of the downloaded file in bytes - downloadUrl: Original MEGA download URL - status: Status of the download operation (always "downloaded") - localPath: Local path where the file was downloaded - kvStoreKey: Key in the KV store where the file is stored - apifyDownloadUrl: URL to download the file from Apify KV store #### Upload Results - fileName: Name of the uploaded file - originalPath: Original path of the uploaded file (local path or URL) - status: Status of the upload operation (always "uploaded") - fileSize: Size of the uploaded file in bytes - megaUrl: Direct MEGA URL for the uploaded file - publicLink: Shareable public link for the uploaded file (if createPublicLink is true) ### Notes 1. For download results, the file is stored in both Apify KV store and locally 2. For upload results, the file is uploaded to MEGA and the original path is preserved 3. All results are stored in the actor's default dataset ## API Usage You can access the MEGA File Uploader & Downloader programmatically from your applications by using the Apify API. To use the Apify API, you'll need an Apify account and your API token, found in Integrations settings in Apify Console. ### Python python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token client = ApifyClient("<YOUR_API_TOKEN>") # Prepare the Actor input run_input = { "action": "upload", # or "download" "email": "your@email.com", "password": "your_password", "filesToUpload": ["path/to/file1", "path/to/file2"], # For download action: # "megaUrls": ["https://mega.nz/file/..."], # "downloadLimitMB": 1000, } # Run the Actor and wait for it to finish run = client.actor("code-node-tools/mega-uploader-downloader---no-download-limit").call(run_input=run_input) # Fetch and print Actor results from the run's dataset for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) ### JavaScript javascript const Apify = require('apify'); // Initialize the ApifyClient with your Apify API token const client = new Apify.Client({ token: '<YOUR_API_TOKEN>', }); // Prepare the Actor input const runInput = { "action": "upload", # or "download" "email": "your@email.com", "password": "your_password", "filesToUpload": ["path/to/file1", "path/to/file2"], # For download action: # "megaUrls": ["https://mega.nz/file/..."], # "downloadLimitMB": 1000, }; // Run the Actor and wait for it to finish const run = await client.actor("code-node-tools/mega-uploader-downloader---no-download-limit").call(runInput); // Fetch and print Actor results from the run's dataset const items = await client.dataset(run["defaultDatasetId"]).iterateItems(); for (const item of items) { console.log(item); } ### CLI bash apify call code-node-tools/mega-uploader-downloader---no-download-limit \ --input '{ "action": "upload", "email": "your@email.com", "password": "your_password", "filesToUpload": ["path/to/file1", "path/to/file2"] }' ### HTTP bash # Using curl curl -X POST https://api.apify.com/v2/acts/code-node-tools~mega-uploader-downloader---no-download-limit/runs \ -H "Authorization: Bearer <YOUR_API_TOKEN>" \ -H "Content-Type: application/json" \ -d '{ "action": "upload", "email": "your@email.com", "password": "your_password", "filesToUpload": ["path/to/file1", "path/to/file2"] }' ### Notes 1. Replace <YOUR_API_TOKEN> with your actual Apify API token 2. For download actions, provide megaUrls instead of email and password 3. The results will be available in the run's default dataset json [ { "fileName": "uploaded_name.txt", "originalPath": "local/file1.txt", "status": "uploaded", "fileSize": 1024, "megaUrl": "https://mega.nz/file/ABCDEF#key", "publicLink": "https://mega.nz/file/ABCDEF#key" "publicLink": "https://mega.nz/file/abc#key" } ] ## Security - Store credentials using Apify Secrets or environment variables - Never log sensitive information - Use the proxyConfig option for additional security if needed ## Use Cases - 🚀 Bypass MEGA download limit for large file downloads - 🔁 Automate backups to MEGA.nz cloud - 📤 Upload files to MEGA without using their web interface - 🔗 Download MEGA public links easily into Apify - 📡 Schedule uploads/downloads via Apify's task runner - 🎥 Download MEGA videos and assets for processing ## Frequently Asked Questions (FAQ) ### ❓ How do I bypass MEGA download limit or transfer quota exceeded error? This actor helps bypass MEGA's download restrictions by routing downloads through the Apify cloud infrastructure. You don’t need a premium MEGA account. ### ❓ Can I use this to upload large files to MEGA automatically? Yes! As long as you provide valid credentials and the files are within MEGA’s file size restrictions, uploads are handled automatically. ### ❓ Is it legal to bypass MEGA download limits? Using automation to download public files that you have the right to access is generally acceptable. However, avoid violating MEGA's terms of service or using this for copyrighted content. ### ❓ Does it support MEGA folders and batch downloads? Yes. You can enable downloadAll to download folders and provide multiple URLs in megaUrls to process them in batch. ### ❓ Can it generate public links after uploading? Yes, set createPublicLink to true in the input, and the Actor will return shareable MEGA links. ### ❓ Where are the files stored? Files are downloaded locally inside the Actor and uploaded to Apify KV Store. The apifyDownloadUrl provides a direct download link. ### ❓ Can I schedule this for automation? Yes! Use Apify’s built-in scheduler to run this Actor periodically (e.g., daily uploads/backups). ## Error Handling The actor handles various error scenarios: - Invalid MEGA URLs - File not found errors - Authentication failures - Network timeouts - File size limit violations All errors are logged and included in the output results. ## Support For issues or questions, please check the documentation or contact support.