megaget(1)


Table of Contents

1. NAME
2. SYNOPSIS
3. DESCRIPTION
4. OPTIONS
5. EXAMPLES
6. REMOTE FILESYSTEM
7. SEE ALSO
8. MEGATOOLS
9. BUGS
10. AUTHOR

1. NAME

megaget - download files from your Mega.co.nz account

2. SYNOPSIS

megaget [--no-progress] [--path <path>] <remotepaths>…
megaget --path - <remotefile>

3. DESCRIPTION

Downloads files from your Mega.co.nz account.

NOTE: If you want to download entire directories, use megasync(1).

4. OPTIONS

--path <path>

Local path to download 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 downloaded to a specified file (this only works if you specify exactly one remote path).

If <path> is -, remote file will be streamed to stdout.

--no-progress
Disable download progress reporting. This is implied when streaming.
-u <email> , --username <email>
Account username (email)
-p <password> , --password <password>
Account password
--config <path>
Load configuration from a file
--ignore-config-file
Disable loading .megarc
--no-ask-password
Never ask interactively for a password
--disable-previews
Never generate and upload file previews, when uploading new files
--reload
Reload filesystem cache
--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.co.nz API calls
  • fs: Dump Mega.co.nz filesystem (may require --reload to actually print something)
  • cache: Dump cache contents
--version
Show version information
<remotepaths>
One or more remote files to download.
<remotefile>
Remote path to a single file to stream.

5. EXAMPLES

  • Download file to the current directory:

    $ megals /Root
    
    /Root
    /Root/README
    
    $ megaget /Root/README
    $ ls
    
    README

6. REMOTE FILESYSTEM

Mega.co.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.co.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.co.nz web client moves deleted files. This directory is not used by megatools when removing files.
/Inbox
Not sure.
/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.

7. SEE ALSO

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

8. MEGATOOLS

Part of the megatools(7) suite.

9. BUGS

Report bugs at https://github.com/megous/megatools or megous@megous.com.

10. AUTHOR

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

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