megatools-copy(1)

📦
version 1.11.5 · 8 versions
, in debian trixie, ubuntu questing

💖 megatools-copy 💖

okay bestie so this is megatools-copy, part of the megatools(1) family (manual section 1, she's that girl). buckle up, we're moving files 🦋

🌸 NAME 🌸

megatools copy — upload/download entire directories to/from your Mega.nz account. yes, whole directories. she does the most. 💅

✨ SYNOPSIS ✨

megatools copy [-n] [--no-progress] --local <path> --remote <remotepath>
megatools copy [-n] [--no-progress] --download --local <path> --remote <remotepath>

🎀 DESCRIPTION 🎀

She syncs remote and local directories. That's the whole vibe. No files are ever overwritten or removed. periodt, nothing gets deleted, nothing gets clobbered, she is a safe girl. 🫶

The default direction is upload — files go up to the cloud. If you want to go the other way and pull files down, you have to add --download. that's it, that's the rule. ✨

💅 OPTIONS 💅

  • -r <remotepath>, --remote <remotepath> — the remote directory path. where in the cloud we're living today. ☁️
  • -l <path>, --local <path> — the local directory path. your actual computer, bestie. 💻
  • -d, --download — download files from the Mega.nz. the default is to upload, so this is you flipping the direction. 🔄
  • -n, --dryrun — don't actually do anything, just print what would be done. like a rehearsal, no commitment. 🙈
  • --no-progress — disable upload progress reporting. if the little bar is stressing you out, turn it off. 😌
  • --enable-previews — generate and upload file previews, when uploading new files. this is the default, unless you changed it in the configuration file. use this to override the option from the configuration file. 🌈
  • --disable-previews — don't generate and upload file previews. default is to generate previews. so this is you saying "no thanks to the thumbnails". 🚫
  • --disable-resume — don't resume downloads from partially downloaded file. default is to resume. so by default she picks up where she left off, and this option is you being like "start over, idc". 💀
  • -u <email>, --username <email> — account username (email). 📧
  • -p <password>, --password <password> — account password. 🤫
  • --no-ask-password — never ask interactively for a password. no prompts, no waiting. 🔒
  • --reload — reload filesystem cache. refresh her memory, she forgot. 🧠
  • --limit-speed <speed> — set maximum allowed upload and download speed in KiB/s. this option overrides config file settings. 0 means no limit. when using ParallelTransfers > 1, upload speed limit is applied to each transfer individually. so like, per-transfer, not global, iykyk. 🏃‍♀️
  • --proxy <proxy> — use proxy server to connect to mega.nz. this option overrides config file settings. more information can be found in libcurl documentation at ⟨https://curl.haxx.se/libcurl/c/CURLOPT_PROXY.html⟩. some acceptable values are:
    • none : Disable proxy if it was enabled in the config file.
    • socks5://localhost:9050 : Local SOCKSv5 proxy server
    • socks5h://localhost:9050 : Local SOCKSv5 proxy server with DNS handled by the proxy
  • --netif <ifname|ip> — network interface or local IP address used for outgoing connections. you have to specify IP address bound to some of your local network interfaces, when specifying an IP address. yes, actually bound to one. don't just say any IP. 😤
  • --ip-proto <proto> — which IP protocol to prefer when connecting to mega.nz (v4, v6, or any). this is just an advisory option. Megatools will resolve mega.nz domain, and then use an A or AAAA record based on the stated preference. it's a suggestion, not a demand. 💁‍♀️
  • --config <path> — load configuration from a file. 📁
  • --ignore-config-file — disable loading .megarc. bye bye config file. 👋
  • --debug [<options>] — enable debugging of various aspects of the megatools operation. you may enable multiple debugging options separated by commas. (eg. --debug api,fs) available options are:
    • http: Dump HTTP request/response details (can be used to debug connection/proxy issues)
    • api: Dump Mega.nz API calls
    • fs: Dump Mega.nz filesystem (may require --reload to actually print something)
    • cache: Dump cache contents
    • tman: Dump transfer manager events
  • --version — show version information. ⭐

🌟 EXAMPLES 🌟

  • Upload directory. ⬆️
$ megatools copy --local MyBackups --remote /Root/Backups
  • Download directory. ⬇️
$ megatools copy --local MyBackups --remote /Root/Backups --download

🦋 REMOTE FILESYSTEM 🦋

Mega.nz filesystem is represented as a tree of nodes of various types. Nodes are identified by a 8 character node handles (eg. 7Fdi3ZjC). Structure of the filesystem is not encrypted. 🌳

Megatools maps node tree structure to a traditional filesystem paths (eg. /Root/SomeFile.DAT).

NOTE: By the nature of Mega.nz storage, several files in the directory can have the same name. To allow access to such files, the names of conflicting files are extended by appending dot and their node handle like this:
/Root/conflictingfile
/Root/conflictingfile.7Fdi3ZjC
/Root/conflictingfile.mEU23aSD

You need to be aware of several special folders:

  • /Root — Writable directory representing the root of the filesystem. 👑
  • /Trash — Trash directory where Mega.nz web client moves deleted files. This directory is not used by megatools when removing files. 🗑️
  • /Inbox — Not sure. 🤷‍♀️ (yes that's literally what the manual says, iconic honestly)
  • /Contacts — Directory containing subdirectories representing your contacts list. If you want to add contacts to the list, simply create subdirectory named after the contact you want to add. 📇
  • /Contacts/<email> — Directories representing individual contacts in your contacts list. These directories contain folders that others shared with you. All shared files are read-only, at the moment. 🔒

🌈 SEE ALSO 🌈

megatools(1), megarc(5), megatools-df(1), megatools-dl(1), megatools-get(1), megatools-ls(1), megatools-mkdir(1), megatools-put(1), megatools-reg(1), megatools-rm(1), megatools-copy(1).

go read the rest of the family, they're all serving. 💜

🧚 MEGATOOLS 🧚

Part of the megatools(1) suite of commands.

💀 BUGS 💀

There is no upstream support for bugreports and feature requests. 😭 but you can send code patches to megatools@xff.cz ⟨mailto:megatools@xff.cz⟩ to get them integrated into upstream repository. bring your patch, bestie, they'll take it. 🫶

👑 AUTHOR 👑

Megatools was written by Ondrej Jirman < megatools@xff.cz ⟨mailto:megatools@xff.cz⟩ >, 2013-2022.

Official website is ⟨https://xff.cz/megatools/⟩. ⭐

and that's the whole page, fr fr — this one's from 11 July 2025 and it's the megatools-copy(1) page, mwah 💖

📦 where this page comes from