Hash Generator

Which hash should you use?

A hash is a fixed-length fingerprint of any input. Change one byte and the fingerprint changes completely, which makes hashes ideal for checking that a file or message arrived unmodified. SHA-256 is the safe default for anything new. SHA-512 is the same family with a longer digest. SHA-1 and MD5 are broken for security purposes but still appear everywhere as checksums, cache keys and legacy API signatures, so you need to be able to produce them.

Common use cases in RPA & automation

• Verifying a downloaded file against the checksum published by the vendor before a robot installs or processes it
• Computing an HMAC-SHA256 signature for an API request, or verifying a webhook payload received by an Integration Service trigger
• Building a stable, unique key for a queue item or a document from its content, so the same invoice is never processed twice
• Detecting whether a report, config file or web page changed since the last run without storing the full content
• Reproducing a hash a legacy system expects, such as MD5 for an old SOAP service or SHA-1 for a Git object id

The same thing in UiPath and .NET

To compute SHA-256 inside a workflow, an Invoke Code or Assign with VB.NET is enough:

hash = BitConverter.ToString(System.Security.Cryptography.SHA256.HashData(System.Text.Encoding.UTF8.GetBytes(text))).Replace("-", "").ToLower()

Use this page to confirm your workflow produces the same digest as the provider, and remember that encoding matters: hashing UTF-8 bytes and UTF-16 bytes of the same text gives different results.