Issue a certificate
Create a record for an eligible stored asset, with a version label, issue date and a SHA-256 file fingerprint.
Turn brand assets into verifiable records. Give clients, teams and partners a public link to check a certificate’s status and compare a file with the version your workspace issued.
Create a record for an eligible stored asset, with a version label, issue date and a SHA-256 file fingerprint.
Send the verification link or code. Recipients can check the record without creating an account or opening your private workspace.
A recipient can select a local file to check whether its exact bytes match the issued asset. The comparison happens in their browser.
Review certificate history and revoke a record when it should no longer be relied on. The public result reflects its current status.
Use a Studio or Agency workspace. Open the brand portal and select Brand Verify. An owner or authorised brand manager issues certificates.
Upload the file to the brand first, complete any required approval, then choose it in Verify. Enter a meaningful version label. Eligible files must be complete and no larger than 25 MB.
Create the certificate and copy its public verification link. Share the link with the asset at delivery, approval or client handoff.
Recipients open the link or enter its code, then optionally compare a file locally. Revoke a certificate when it is no longer valid; issue a new record for a new version.
Give clients a clear record for delivered identity files and reduce “which version is this?” follow-ups.
Check that a shared file matches the version issued by the workspace before sending it into production.
Keep each client’s certificate history alongside its brand assets, with controlled issuance and a public check for recipients.
Brandguide IO brings guidelines, asset management and verification into the same workflow. The file, its version and its certificate are connected to the brand workspace your team already uses.
That combination is the difference: a practical check at the point of handoff, backed by an ongoing record you can revoke. It helps reduce version confusion, makes changes detectable and gives recipients a repeatable way to check a file.
A matching file has the same bytes as the certified asset. An edited, re-exported or compressed copy can look identical and still produce a different result.
A certificate records issuance by an authorised workspace user. It does not independently prove legal ownership, identify the original creator, certify a physical product or prevent someone from copying a file. Public certificate details are visible to people with the link; the private source file is not published by the verifier.
New certificate issuance is available on eligible Studio and Agency workspaces, including their active trials. Starter does not include issuance. Existing records remain available to check, and authorised users can revoke certificates after a downgrade or expiry.