HCXHASH2CAP(1)

πŸŽ€ NAME πŸŽ€

hcxhash2cap β€” it's part of the hcx tools set, bestie 🫢 that's literally the whole vibe of this one.


✨ DESCRIPTION ✨

okay so. This is hcxhash2cap, version 7.1.2, and the copyright belongs to (C) 2026 ZeroBeat πŸ’–. The usage is giving very simple, very iconic:

hcxhash2cap <options>

and here are the options, no gatekeeping 🫢:

  • -c <file> β€” this is your output cap file, periodt.
  • --pmkid-eapol=<file> β€” feed it a PMKID EAPOL (22000) combi hash file, slay πŸ’…
  • --pmkid=<file> β€” feed it a PMKID (16800) hash file. heads up bestie, this one is deprecated 😭
  • --hccapx=<file> β€” feed it an hccapx (2500) hash file. also deprecated, rip πŸ™ˆ
  • --hccap=<file> β€” feed it an hccap (2500) file. this one is ancient fr fr, like museum-tier πŸ’€
  • --john=<file> β€” feed it a John the Ripper WPAPSK hash file 🧚
  • -h, --help β€” show this help πŸŽ€
  • -v, --version β€” show version ⭐

and the little detail that lowkey matters a lot: if you don't pick a cap file with -c, the output is written to single cap files instead, and the format goes like this:

mac_sta.cap (mac_sta.cap_x)

so you get that naming whether you asked for it or not, no cap 🫑


important notice, and bestie I need you to actually read this one πŸ˜­πŸ’€: conversion from a dump file to a hash file is not loss less. So hash files that contain EAPOL M3 MESSAGEs can't be converted back to a cap file. That's the rule, that's the limit, don't come for me, come for the format πŸ€·β€β™€οΈ

and that's the whole page, you ate it πŸ’–πŸ‘‘ β€” this was hcxhash2cap 7.1.2, (C) 2026 ZeroBeat, dated July 2026, and yes the manual name really is HCXHASH2CAP(1). bye pookie, go convert something responsibly πŸŒΈπŸ¦‹

πŸ“¦ where this page comes from