Why 5 Files Are More Than Enough

The 5-file limit is usually enough because most serious proof workflows should not certify every single source file one by one.

That would create unnecessary fragmentation, more records to manage, more room for confusion later, and would also incur unnecessary extra cost.

A better practice is to export the relevant state of the project into a single archive file such as .zip, then certify that archive as the complete package for that version.

• One archive represents the full project state at that exact moment.
• One certification produces one hash and one timestamped proof trail.
• It is easier to explain later than dozens or hundreds of individual file records.
• It reduces the risk of forgetting supporting assets, folders, or dependencies.
• It keeps the evidence chain cleaner because the certified object is the exact archive you retained.

Think of it like hashing: you do not usually certify every file in a large project separately if what matters is the integrity of the project as a whole. You package the full set, certify that package, and preserve it.

• Prepare the project version you want to preserve.
• Remove temporary junk only if it is truly irrelevant to the record.
• Create a single archive file of the full project folder.
• Name it clearly with project name and version or date.
• Upload that archive to Niveusly and certify it.
• Keep the exact certified archive in your own storage and backups.

Use multiple files only when that separation has real evidentiary value.

• A main archive plus a separate exported PDF deliverable.
• A source package plus a signed agreement or brief.
• Different artifacts that were created and shared as distinct deliverables.

Even then, five files is enough for most milestones because you are usually proving a version package, not every internal file individually.