Batch Timestamps Guide: Timestamp Hundreds of Files at Once

When to Use Batch Timestamps

Single-file timestamping is perfect for one-off needs — a contract, a final design, a photo. But many situations call for batch processing:

• End-of-day archival: Timestamp all files created or modified today
• Project milestones: Timestamp all deliverables at once when a milestone is complete
• Portfolio protection: Timestamp your entire creative portfolio in one session
• Release builds: Timestamp all artifacts from a software release
• Compliance records: Timestamp a batch of regulatory documents

Step-by-Step: Batch Timestamping

Step 1: Prepare Your Files

Gather all files you want to timestamp. They can be any type, any size, in any folder structure. The only requirement: each file must be accessible on your device.

Tip: For large batches, organize files in a single folder or use a ZIP archive. Timestamping the ZIP creates proof of the entire collection as a unit.

Step 2: Choose Your Timestamp Type

Need	Mode	Cost	Speed
Immediate proof	Instant	2 credits/file	Seconds
Cost-efficient batch	Scheduled	1 credit/file	Next batch window

For most batch operations, scheduled is the right choice. It uses half the credits of instant mode, and the slight anchoring delay is usually irrelevant for batch archival.

Step 3: Select Files

In the TimeProof web interface, drag multiple files onto the timestamp area, or click to browse and select multiple files.

Each file’s SHA-256 hash is computed locally in your browser. The files themselves are never uploaded.

Step 4: Submit the Batch

Click “Timestamp All” to submit the batch. For instant timestamps, each file is anchored within seconds. For scheduled timestamps, files are queued for the next batch window.

Step 5: Download Certificates

Each file receives its own individual certificate containing:

• The file’s unique SHA-256 hash
• The Merkle proof (path from hash to root)
• The blockchain transaction hash
• The anchor timestamp (block time)
• Verification instructions

Important: Download and organize certificates alongside your original files. Each certificate is a self-contained proof document.

Organizing Your Certificates

By project

Project A/
  deliverables/
    logo-final.ai
    logo-final-timestamp.pdf
    brochure-v3.pdf
    brochure-v3-timestamp.pdf

By date

2025/
  03-March/
    2025-03-15-batch/
      [file1 + certificate]
      [file2 + certificate]

Archive approach

timestamps/
  2025-Q1/
    certificates/
    original-files/

Choose whatever structure fits your workflow. The key is keeping certificates paired with their original files so you can verify any file at any time.

Cost Planning

Individual creator

Monthly Volume	Typical Mode	Credits Needed	Example Path
50 files	Scheduled	50	Micro pack ($15, 100 credits)
100 files	Scheduled	100	Micro pack ($15, 100 credits)
200 files	Scheduled	200	Basic pack ($49, 350 credits)

Small business

Monthly Volume	Typical Mode	Credits Needed	Example Path
500 files	Scheduled	500	Pro pack ($129, 1,000 credits) or Pro plan
1,000 files	Scheduled	1,000	Pro pack ($129, 1,000 credits)
2,000 files	Scheduled	2,000	Bulk pack ($299, 2,500 credits) or Business plan

The ZIP Archive Strategy

For very large batches where individual file certificates aren’t needed, consider:

1. Place all files in a folder
2. Create a ZIP archive of the folder
3. Timestamp the single ZIP file = 1 timestamp

The ZIP’s hash proves the exact contents of the entire collection. To verify any individual file, someone would need the ZIP, extract it, and confirm the contents. This is less convenient than individual certificates but costs a single timestamp for any number of files.

Batch + Legal-Grade

For batches that need court-ready evidence (legal discovery, regulatory submissions), add Legal-Grade:

• Starter and Pro: 50 credits for up to 25 files, then +2 credits per file after 25
• Business plan: 25 credits for up to 25 files, then +1 credit per file after 25
• Enterprise plan: included at 0 extra credits
• A batch of 50 scheduled files with Legal-Grade uses 150 credits on Starter or Pro, 100 credits on Business, and 50 credits on Enterprise

This means Legal-Grade becomes more cost-effective as the batch grows, because the per-batch upgrade is amortized across more files.

Verification for Batch Files

Each file from a batch is independently verifiable:

1. Re-hash the file: Compute SHA-256 of the original file
2. Check certificate: Confirm the hash matches your certificate
3. Verify Merkle proof: Walk the proof from hash to root
4. Check blockchain: Confirm the root exists on Polygon at the stated time

The batch structure is invisible during verification — each file’s certificate is fully self-contained. The verifier doesn’t need to know about other files in the batch, doesn’t need the original batch, and can verify using any SHA-256 tool and Polygonscan.

Best Practices

1. Timestamp before sharing: Batch-timestamp all deliverables before sending to clients
2. Regular schedule: Set a weekly or monthly timestamp session for new work
3. Include metadata: Name files clearly so certificates are meaningful even years later
4. Backup certificates: Store certificates in at least two locations (local + cloud)
5. Test verification: Periodically verify a random certificate to confirm your process works