megatools-export(1)

✨ megatools-export ✨

okay bestie, this is the man page for megatools-export β€” part of the megatools suite. it's giving "i just want a public link, please and thank you" πŸ’…


🌸 NAME 🌸

megatools export β€” create public links for remote files 🫢


πŸ¦‹ SYNOPSIS πŸ¦‹

megatools export <remotepaths>...

πŸ’– DESCRIPTION πŸ’–

So here's the vibe: this command exports (aka creates public links) for all the files chillin' in your mega.nz account, and you point at them with <remotepaths>. πŸŽ€

Heads up though β€” it works only for individual files for now. no folders, bestie. not yet. 😭

πŸ‘‘ OPTIONS πŸ‘‘

  • -u <email>, --username <email> β€” your account username, which is literally just your email. that's it, that's the whole thing. ✨
  • -p <password>, --password <password> β€” your account password. keep it secret, keep it safe. πŸ”
  • --no-ask-password β€” never, ever ask interactively for a password. like, don't even try. πŸ™ˆ
  • --reload β€” reload the filesystem cache. fresh start energy. 🌈
  • --limit-speed <speed> β€” sets the max allowed upload AND download speed, measured in KiB/s. this option overrides whatever your config file says. 0 means no limit (go off, i guess πŸ’€). when you're using ParallelTransfers > 1, the upload speed limit gets applied to each transfer individually. no cap.
  • --proxy <proxy> β€” use a proxy server to connect to mega.nz. this overrides your config file settings too. more deets live in the 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> β€” the network interface or local IP address used for outgoing connections. ⚠️ if you're specifying an IP address, you have to specify an IP address that's bound to one of your local network interfaces. no random IPs, babe.
  • --ip-proto <proto> β€” which IP protocol to prefer when connecting to mega.nz: v4, v6, or any. it's just advisory, not a demand β€” megatools will resolve the mega.nz domain and then use an A or AAAA record based on the preference you stated. 🌐
  • --config <path> β€” load configuration from a file. πŸ“
  • --ignore-config-file β€” disable loading .megarc. bye bye config. πŸ‘‹
  • --debug [<options>] β€” enable debugging for various aspects of megatools operation. you can turn on multiple debugging options at once, separated by commas (eg. --debug api,fs). πŸ›

the 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. ⭐
  • <remotepaths> β€” one or more remote filesystem file paths to export.

πŸŽ€ EXAMPLES πŸŽ€

  • export a file:
$ megatools export /Root/README
https://mega.nz/#!OFFRlbgR!k5rWmLp3mxB0gsq07Ii67PLd9L0wq4KondFLDlfH3Uw

🧚 REMOTE FILESYSTEM 🧚

Mega.nz's filesystem is represented as a tree of nodes of various types. 🌳 nodes are identified by an 8 character node handle (eg. 7Fdi3ZjC). and ngl, the structure of the filesystem is not encrypted.

megatools maps that node tree structure onto traditional filesystem paths (eg. /Root/SomeFile.DAT). so cute, so familiar.

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

you need to be aware of several special folders, bestie, don't skip these:

  • /Root β€” writable directory representing the root of the filesystem.
  • /Trash β€” trash directory where the Mega.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 a 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).


🌟 MEGATOOLS 🌟

part of the megatools(1) suite of commands. family. 🫢


πŸ’€ 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 the upstream repository. be the change you want to see, babe. πŸ”₯


🌸 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, bestie β€” this one's from 11 July 2025, the megatools-export(1) manual page. go forth and export those links. periodt. πŸ’…βœ¨

πŸ“¦ where this page comes from