FILE TOOL // 042

File Digital Signature Verifier

Check whether a file still matches a Callfile ECDSA signature bundle, using the bundled public key and the file's exact current bytes.

Processed locally in your browser

Choose file and signature bundle

Original file plus .signature.json

Drop files here Select exactly two files: the file to verify and its Callfile JSON signature bundle.

FileSizeType

No files selected.

Bundle suffix Verification mode Name check Report format

Check recorded size

Choose files to begin.0 files

How to use File Digital Signature Verifier

Select exactly two files: the file to verify and its Callfile JSON signature bundle.
Adjust the options for the report you need.
Select “Verify Signature,” review the result, and download the generated file.

What this file tool does

Check whether a file still matches a Callfile ECDSA signature bundle, using the bundled public key and the file's exact current bytes.

The verifier imports the public JWK from the bundle, verifies the ECDSA signature over the selected file bytes, and separately compares the recorded digest.

Processing stays on this device. Requires a Callfile signature-v1 JSON bundle and its corresponding file. Verification confirms byte integrity and key possession, not a person's identity.

Supported inputs and limits

Requires a Callfile signature-v1 JSON bundle and its corresponding file. Verification confirms byte integrity and key possession, not a person's identity.

Inputs	One source file + one signature JSON
Validation	ECDSA signature and recorded digest
Result	Downloadable JSON report
Identity	Not certificate-backed

Example and practical tips

Practical example

After downloading a signed package, select the package and its signature JSON. A valid result means the bytes match the signature created by the bundle's key.

Tips

Do not edit the JSON bundle before verification.
A valid signature does not automatically mean the file is safe.
Confirm the public-key source when identity matters.

Frequently asked questions

How do I verify an ECDSA file signature?

Select the original file and its Callfile signature JSON, then run verification.

What does a valid digital signature prove?

It proves that the exact bytes were signed by the private key matching the bundled public key.

Why is my file signature invalid after downloading?

The file may have changed, the wrong bundle may be selected, or the bundle itself may be damaged.

Can I verify signatures made by OpenSSL or GPG here?

No. This page expects the Callfile signature-v1 JSON structure and Web Crypto-compatible ECDSA values.

Does a valid signature mean the file has no malware?

No. Signature validity checks integrity and key matching; it is not a malware scan.

Related file tools

File Digital Signature Creator File Checksum Verifier Checksum Generator Hash Manifest Generator

File Digital Signature Verifier details

Tool number	042
Category	Integrity & Verification
Processing	Local browser operation
Download	Generated report or verification bundle

Browse more file tools

Callfile categories

File Organization & Naming

Rename, clean, sequence, and validate file names.

View all

Archive & Compression

Create, inspect, compress, and extract archives.

View all

Integrity & Verification

Generate checksums, manifests, and signatures.

View all

File Inspection & Analysis

Inspect bytes, headers, MIME types, and entropy.

View all

Folder & Storage Analysis

Analyze folder size, contents, age, and distribution.

View all

File Splitting & Assembly

Split, join, extract, patch, and verify chunks.

View all

File Security & Privacy

Encrypt files and inspect privacy or safety signals.

View all

Backup & Change Tracking

Compare backup sets and detect file changes.

View all