MEGAPUT(1)

πŸ“¦ version 1.10.3, in ubuntu jammy

πŸ’– MEGAPUT(1) β€” the megatools manual, but make it cute πŸ’–

okay bestie, welcome to megaput, the part of the megatools suite that yeets your files up into your Mega.nz account. πŸ¦‹βœ¨


✨ NAME ✨

megaput β€” upload files to your Mega.nz account. that's it. that's the job. πŸ’…


🌸 SYNOPSIS 🌸

megaput [--no-progress] [--path <remotepath>] <paths>...

πŸ’« DESCRIPTION πŸ’«

Uploads files to your Mega.nz account. iconic behaviour, honestly. πŸ‘‘

NOTE: If you want to upload entire directories, use megacopy(1) instead. megaput is a one-file-at-a-time kinda girlie, don't make her carry the whole folder. 🫢

πŸŽ€ OPTIONS πŸŽ€

  • --path <remotepath> β€” Remote path to upload to. If this path is a directory, files are placed into the directory. If this path doesn't exist, and its parent directory does, the file will be uploaded to a specified path β€” and heads up, this only works if you specify exactly one file. one (1) file. no more. πŸ™ˆ
  • --no-progress β€” Disable upload progress reporting. for when the little progress bar is giving you anxiety. 😭
  • --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. basically: "yes previews please, idc what the config says." ✨
  • --disable-previews β€” Don't generate and upload file previews. Default is to generate previews. so if you pass this, you're the one going against the grain. πŸ’€
  • -u <email>, --username <email> β€” Account username (email). yes it's your email. no it's not your @. 🌈
  • -p <password>, --password <password> β€” Account password. keep it secret, keep it safe. πŸ”’
  • --no-ask-password β€” Never ask interactively for a password. she will NOT be prompting you. not today. 🚫
  • --reload β€” Reload filesystem cache. fresh eyes, fresh cache, slay. 🧚
  • --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 the number is per transfer, not a group budget β€” math matters bestie. πŸ“)
  • --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
  • --config <path> β€” Load configuration from a file. choose your own adventure, but it's a file path. πŸ—‚οΈ
  • --ignore-config-file β€” Disable loading .megarc. she's going rogue. no config, just vibes. πŸ’…
  • --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
lowkey the fs one is sneaky β€” it may require --reload to actually print something. don't come for me if it's quiet. 🀫
  • --version β€” Show version information. who are you, what build is this, spill. πŸ“’
  • <paths> β€” One or more local files to upload. plural. many. the more the merrier. πŸ“

πŸ”₯ EXAMPLES πŸ”₯

  • Upload file to the /Root:
$ megaput README
$ megals /Root

/Root
/Root/README
  • Upload file, while naming it differently:
$ megaput --path /Root/README.TXT README
$ megals /Root

/Root
/Root/README.TXT

see how she just... renamed it on the way up? main character energy. πŸ‘‘


πŸ¦‹ 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. your home base. 🏠

πŸ—‘οΈ /Trash

Trash directory where Mega.nz web client moves deleted files. This directory is not used by megatools when removing files. so don't expect megatools to rummage around in there, bestie. πŸ™…

πŸ“₯ /Inbox

Not sure. (yes, that is genuinely what the manual says. iconic honesty. 😭)

πŸ“‡ /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. look but don't touch. πŸ‘€


πŸ‘€ SEE ALSO πŸ‘€

megatools(7), megarc(5), megadf(1), megadl(1), megaget(1), megals(1), megamkdir(1), megaput(1), megareg(1), megarm(1), megacopy(1).


🫢 MEGATOOLS 🫢

Part of the megatools(7) suite. found family fr fr. πŸ’œ


πŸ’€ BUGS πŸ’€

Report bugs at https://github.com/megous/megatools or megous@megous.com. (not me tho, i just do the vibes. 😭)


🌟 AUTHOR 🌟

Megatools was written by Ondrej Jirman <megous@megous.com>, 2013-2016.

Official website is http://megatools.megous.com.


and that's the whole page, bestie β€” this was megatools 1.10.2, dated 04/15/2020, aka the MEGAPUT(1) era. go forth and upload responsibly. πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from