No, minification makes code unreadable for debugging. It is applied at the build stage, before deployment to production, and the working copy is kept in its original form.
A UUID is generated independently on any machine and is almost guaranteed not to match another UUID, which makes it fit for distributed systems. A sequential counter needs a single source and reveals how many records are in the database.
No, MD5 is considered unsafe for that task because of known collisions and how fast it can be brute-forced. For file checksums it is still fine.
Yes, it checks the structure – whether brackets, quotes and commas are correct – not whether the data matches a specific schema or business logic.
Tools for everyday developer tasks: shrinking code before production, checking data structures, parsing request headers and generating service values like UUIDs and hashes.
Minification reduces a file's weight but does not speed up its execution – the effect is on page load time first, not on how fast a script runs.
Minifiers and validators are handy not only run by hand before a release but also as part of a build pipeline: JSON checks and hash generation for file integrity checks are easy to automate. The manual online version comes in useful for a one-off check or debugging a specific fragment, when setting up a local environment for a single check makes no sense.
Some converters overlap with the "Converters and generators" section, but here is gathered specifically the part needed while working with code: Base64 for embedding small files into code, the binary system for low-level debugging, URL encoding for passing parameters correctly in a request.
Technical checks of the site itself – availability, SSL, speed – are covered in Technical SEO & Security. Working with domains and IPs is in Domains & Hosting.