megaput man page
megaput — upload files to your Mega.nz account
megaput [--no-progress] [--path <remotepath>] <paths>...
Uploads files to your Mega.nz account.
NOTE: If you want to upload entire directories, use megacopy(1).
- --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 it’s parent directory does, the file will be uploaded to a specified path (this only works if you specify exactly one file).
Disable upload progress reporting.
Never generate and upload file previews, when uploading new files
- -u <email>, --username <email>
Account username (email)
- -p <password>, --password <password>
Never ask interactively for a password
Reload filesystem cache
- --speed-limit <speed>
Set maximum allowed upload and download speed in KiB/s. This option overrides config file settings. 0 means no limit.
- --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
Disable loading .megarc
- --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:
- api: Dump Mega.nz API calls
- fs: Dump Mega.nz filesystem (may require --reload to actually print something)
- cache: Dump cache contents
Show version information
One or more local files to upload.
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
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:
Writable directory representing the root of the filesystem.
Trash directory where Mega.nz web client moves deleted files. This directory is not used by megatools when removing files.
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.
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.
megatools(7), megarc(5), megadf(1), megadl(1), megaget(1), megals(1), megamkdir(1), megaput(1), megareg(1), megarm(1), megacopy(1).
Part of the megatools(7) suite.
Report bugs at https://github.com/megous/megatools or email@example.com.
Megatools was written by Ondrej Jirman <firstname.lastname@example.org>, 2013-2016.
Official website is http://megatools.megous.com.
megacopy(1), megadf(1), megadl(1), megaget(1), megals(1), megamkdir(1), megarc(5), megareg(1), megarm(1), megatools(7).