Skip to content

File Tools

Compress, hash and convert files locally.

File Tools works on bytes rather than on text. File Hash computes MD5 and SHA-256 for a chosen file so a download can be compared against a published checksum, and JSON File Validator parses a dropped file and reports where it fails. Gzip Compress and Gzip Decompress, together with Deflate Compress and Deflate Decompress, move text to and from compressed payloads carried as Base64, File to Base64 inlines a small asset, and File Extension Info explains what a suffix usually means. chmod Calculator and chmod Decoder translate Unix permission bits in both directions.

Hashes, compression formats, and permissions

A file hash is the fastest way to answer whether something arrived intact. Compare the SHA-256 value against the one the publisher listed; if a single byte changed, every character of the digest changes. MD5 is still published by older projects and is fine for spotting accidental corruption, but it is not collision resistant, so a matching MD5 is not proof that a file is the expected one when the source is untrusted.

Gzip and deflate are not interchangeable, and the errors when you mix them up are unhelpful. Gzip wraps the compressed stream in a header and a checksum trailer, which is why a truncated download fails to decompress. Deflate is the raw stream without either, and some systems add a wrapper of their own. If decompression fails, format mismatch is the more likely cause than corrupt data, so try the other tool before assuming the file is damaged. Output here is Base64 text, which makes it safe to paste into a JSON field or a config value.

Unix permissions are octal arithmetic: read is four, write is two, execute is one, and the three digits stand for owner, group and other. chmod Calculator builds a mode such as 644 or 755 from checkboxes, and chmod Decoder reads a string like -rw-r--r-- back into numbers. Worth remembering that 777 grants write access to everyone who can reach the file.