megatools-reg(1)

πŸ’– megatools-reg πŸ’–

okay so bestie, welcome to megatools-reg from the megatools(1) squad β€” this is the one that makes you a whole new Mega.nz account ✨


✨ SYNOPSIS ✨

megatools reg [--scripted] --register --email <email> --name <realname> --password <password>
megatools reg [--scripted] --verify <state> <link>

πŸ¦‹ DESCRIPTION πŸ¦‹

So you wanna register a new Mega.nz account. Slay. But it's not a one-step thing, it's a two-step glow-up, and you have to do them in order:

  1. --register: makes you a new non-verified account πŸ’…
  2. --verify: confirms the account with the link that got sent to <email> πŸ“©

There's a whole example of the registration flow down below, don't worry, we'll get there. 🫢


πŸŽ€ OPTIONS πŸŽ€

  • --register β€” creates your new non-verified account. Step one of the journey, bb.
  • --verify <state> <link> β€” verifies the account you already made with megatools reg --register. You have to hand it the <state> that came back from megatools reg --register, plus the verification link from the email that was sent to <email>. Both of them, no skipping. ✨
  • --email <email> β€” your email is your new account username, so it's literally what you'll use to sign in. It's giving main character login credential.
⚠️ NOTES: beware that ATM, email format is not validated by megatools. So you could type absolute nonsense and it would just... let you. πŸ™ˆ
  • --name <realname> β€” your real (or fake) name. No judgement here, we don't verify vibes. πŸ’…
  • --password <password> β€” plaintext password. There is zero strength checking happening, so making it a strong one is entirely on you, bestie. Pick good. πŸ”₯
  • --scripted β€” after registration, it prints the command you can use to finish the registration, in a format that's suitable for scripting purposes. Very "hand this off to a robot" energy. πŸ€–
  • --limit-speed <speed> β€” sets the max allowed upload and download speed, measured in KiB/s. This option overrides the config file settings. 0 means no limit at all, go feral. And when you're using ParallelTransfers > 1, the upload speed limit gets applied to each transfer individually.
  • --proxy <proxy> β€” use a proxy server to connect to mega.nz. This option overrides config file settings. More info lives in the libcurl docs 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> β€” the network interface or local IP address used for outgoing connections. Heads up: you have to specify an IP address bound to one of your local network interfaces when you're specifying an IP address. 🧚
  • --ip-proto <proto> β€” which IP protocol to prefer when connecting to mega.nz (v4, v6, or any). This is just an advisory option, so it's a suggestion, not a demand. Megatools resolves the mega.nz domain, and then uses an A or AAAA record based on the stated preference. 🌈
  • --config <path> β€” load configuration from a file. πŸ“
  • --ignore-config-file β€” disables loading .megarc. Sometimes you just don't wanna hear from your config file, y'know? πŸ’€
  • --debug [<options>] β€” enables debugging of various aspects of the megatools operation. You can 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. ⭐

🌸 EXAMPLE 🌸

First, create a non-verified account:

$ megatools reg --register --email your@email.com --name "Your Name" --password "Your Password"

Registration email was sent to test@megous.com. To complete registration, you must run:

  megatools reg --verify vbFFFv7AFM25etzkFXLs9A==:Z7FFbgAAAAAAAAAArL33eA==:inEONh3tmwY @LINK@

(Where @LINK@ is the registration link from the 'MEGA Signup' email)

Now wait for a verification mail and run the command as asked:

$ megatools reg --verify vbFFFv7AFM25etzkFXLs9A==:Z7FFbgAAAAAAAAAArL33eA==:inEONh3tmwY \
    'https://mega.nz/#confirmciyfWXRGFNcM...'

Account registered successfully! πŸŽ‰πŸ‘‘


πŸ‘€ 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). The whole friend group, fr fr. πŸ’–


🧚 MEGATOOLS 🧚

Part of the megatools(1) suite of commands. You're in the family now. 🫢


πŸ’€ 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. So if you fix it yourself, they'll take it β€” that's the vibe. πŸ”₯


πŸ‘‘ AUTHOR πŸ‘‘

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

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


k that's the whole page bestie, go make yourself an account πŸ’œ

This was megatools-reg(1) from the megatools suite, dated 11 July 2025 β€” mwah, ily, go register something ✨

πŸ“¦ where this page comes from