megatools-df(1)

πŸ’– megatools-df β€” the "how much cloud space do I even have" page πŸ’–

okay bestie, sit down, hydrate, and let's talk about megatools df, one of the lil stars of the megatools(1) squad ✨


🌸 NAME 🌸

megatools df β€” show total available, used, or free space in the cloud 🫢


✨ SYNOPSIS ✨

megatools df [--free|--total|--used] [--mb|--gb|-h]

that's it. that's the whole vibe. no cap πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

It shows you the available, used, and free space in the cloud β€” and you can get that tea in either machine readable or human readable format, whichever one your lil heart desires 😌


πŸ‘‘ OPTIONS πŸ‘‘

  • --total β€” only show the total available space, which is literally free + used. the whole pie πŸ₯§
  • --free β€” only show the free space. the leftover crumbs (affectionate) πŸ“
  • --used β€” only show the used space. the part you actually did πŸ‘
  • --human, -h β€” display file sizes in a human readable format. because 53687091200 is not a personality πŸ’€
  • --mb β€” show everything in MiB units.
  • --gb β€” show everything in GiB units.
  • -u <email>, --username <email> β€” account username (that's your email, bestie)
  • -p <password>, --password <password> β€” account password πŸ”
  • --no-ask-password β€” never ask interactively for a password. it will not prompt you, periodt.
  • --reload β€” reload the filesystem cache πŸ”„
  • --limit-speed <speed> β€” set the maximum allowed upload and download speed in KiB/s. this option overrides config file settings. 0 means no limit. when you're using ParallelTransfers > 1, the upload speed limit is applied to each transfer individually β€” so yes, they stack, watch out πŸ‘€
  • --proxy <proxy> β€” use a proxy server to connect to mega.nz. this option overrides config file settings. more info lives 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> β€” network interface or local IP address used for outgoing connections. you have to specify an IP address that's bound to one of your local network interfaces when you're specifying an IP address. no random IPs, babe πŸ™ˆ
  • --ip-proto <proto> β€” which IP protocol to prefer when connecting to mega.nz (v4, v6, or any). this is just an advisory option β€” megatools will resolve the mega.nz domain, and then use an A or AAAA record based on the stated preference. it's giving "suggestion, not a demand" πŸ’
  • --config <path> β€” load configuration from a file
  • --ignore-config-file β€” disable loading .megarc
  • --debug [<options>] β€” enable 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 ⭐

🌈 EXAMPLES 🌈

  • show overall human readable space usage information:
$ megatools df -h
Total: 50.0 GiB
Used:  6.4 GiB
Free:  43.6 GiB
  • check free space from a script:
$ test `megatools df --free --gb` -lt 1 && \
  echo "You have less than 1 GiB of available free space"

script girlies stay winning 🫑


πŸ’€ KNOWN BUGS πŸ’€

megadf can't determine available space for premium accounts. yeah. it just can't. not its fault, not yours, we move on 🧚


πŸŽ€ 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. iconic lineage honestly πŸ‘‘


πŸ”₯ BUGS πŸ”₯

there is no upstream support for bugreports and feature requests. but you can send code patches to megatools@xff.cz to get them integrated into the upstream repository. so like, bring a fix, not a complaint πŸ’…


πŸ’œ AUTHOR πŸ’œ

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

official website is https://xff.cz/megatools/ ✨


and that's the whole page, bestie β€” megatools-df(1), dated 11 July 2025, straight from the megatools-df(1) manual. now go check your cloud space, you gorgeous nerd πŸ«ΆπŸ’–
πŸ“¦ where this page comes from