ReviewProof ⚖

Paste import or file upload: which should you use?

By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026

Run the free review audit See pricing · See a sample provenance report

Short answer

Use file upload for the historical import and anything near your plan cap; use paste for small top-ups — a week's reviews copied from a spreadsheet, a single source's export you want analysed before filing. Both routes run the same parser (header row required, flexible column names), the same caps (500 Free / 5,000 Pro / 50,000 Agency per import) and produce identical records. The choice is about error control: a file can be re-checked before it is committed; a paste is only as good as your clipboard.

What is paste import?

Paste import is entering CSV text directly into the audit desk rather than uploading a file. The parsing is the same code — columns matched by name, rows without body text skipped, ratings clamped to the 0–5 range, verified flags read from yes/true/1-style values — so the distinction is purely operational: how the text was prepared, how large it is, and whether a durable source file exists behind the import for later checking.

Where paste genuinely wins

Paste wins on speed for small, well-formed batches: the weekly export from one till system, a dozen reviews collected through your own request flow, a quick re-check of a single source before a meeting. It also wins for diagnosis — paste twenty rows, read the report, and you have verified your column mapping before committing two thousand. The failure mode to respect is silent truncation and clipboard mangling: a spreadsheet copied through a rich-text editor can mangle commas inside review text, splitting a row mid-sentence. If the imported count differs from the rows you copied, stop and use the file; the parser skipped or split something, and the report's totals are your tripwire.

The workflow is the same on every plan, and the free tier does the complete job for one location: import by CSV upload or paste (up to 500 reviews per import on Free), read the full risk analysis and report, open a provenance certificate for any review, and publish the verified-experience widget. Pro ($29/month, 3 locations, 5,000 reviews per import) adds the full provenance chain detail, the evidence export, AI reply drafts and the reviewer-fraud graph. Agency ($79/month, 50,000 reviews per import) is the multi-location tier. Nothing about the free audit is a sample or a teaser — the report you get free is the real analysis of your real rows.

Where the file is non-negotiable

Anything you may need to re-produce needs a file: the initial history, any import an evidence pack will later cite, any chunked multi-part import where order matters. Keep the source file, unedited, beside the dated evidence pack — together they let a sceptic re-run your audit and land on your numbers, which is the deepest form the proof takes. Name files by location and period and never overwrite a source with a 'cleaned' version; corrections go in a new file with a note, exactly as chain events append rather than rewrite. The paste box is a convenience for the rhythm; the file archive is the institution.

After the first audit, the habit that matters is cadence. Re-import on a regular rhythm — monthly suits most locations — so new reviews enter the provenance record while the underlying transactions are still easy to match. Each import logs provenance events, moderation starts from kept (no suppression), and the certificate for any review shows its chain: imported, transaction-linked or not, analysed with its signals, moderated with its decision. A record built gradually like this is worth far more in a dispute than one assembled in a panic the week the dispute arrives.

Mistakes that undo the work

Pasting a near-cap history through a chat or notes app that rewraps lines — the mangling is invisible until counts reconcile badly. Pasting the same batch twice 'to be sure', doubling rows and fingerprints. And the reverse error: uploading an ancient, many-times-edited master spreadsheet as the historical source when cleaner per-source exports exist — the file route's virtue is reproducibility, which a much-edited file has already lost.

A detail worth knowing before you start: ReviewProof analyses what you give it. The CSV importer reads reviewer, rating, title, body, date and source columns, plus a verified-transaction flag and a transaction reference when you have them. Reviews with a transaction link are marked verified; reviews without one are marked UNLINKED — kept in the audit, visible in the report, but excluded from the verified-experience widget, which only displays reviews that are both transaction-linked and in a kept or published state. That single rule is the difference between a widget that markets and a widget that proves.

Worked example: one importer, two habits, zero surprises

A fictional worked example, written to show the numbers and the decisions in practice.

A mobile repair business with 96 historical reviews pasted its history in one go — under the Free cap, done in minutes, counts reconciled against its spreadsheet. It then set its routine: weekly, the owner pastes the week's webshop export (never more than thirty rows) as a top-up; monthly, she downloads the platform exports as files and imports those, archiving each file with the month's evidence summary. In eight months the imported total (412) has matched her source files at every monthly check — a boring sentence that is, in provenance terms, a small triumph of bookkeeping.

Your five-action checklist

  1. Paste for batches well under the cap, from a plain-text-safe source
  2. Verify the imported count against the rows you pasted, every time
  3. Upload files for history, cited imports and multi-chunk work
  4. Archive each source file unedited beside its dated evidence pack
  5. If counts disagree, stop and diagnose — never re-paste and hope

Frequently asked questions

Do paste and upload parse differently?

No. Same parser, same column matching, same caps, same resulting records. Only the preparation and reproducibility differ.

Why did some pasted rows not import?

Rows without body text are skipped, and clipboard mangling can split rows at commas inside review text. Reconcile the count; if it is off, switch to a file upload.

Which route should the first import use?

Almost always a file — the history is the import an evidence pack will cite, and the archived source file lets anyone reproduce the audit.

Are ratings cleaned on import?

Ratings are parsed as numbers and clamped to 0–5; unparseable ratings arrive as 0, which the report will show — another reason to sample-check the first import.

Keep reading

Related guides from the ReviewProof library:

Start with the tool itself: open the free audit desk, see how ReviewProof works, compare Free, Pro and Agency plans, inspect the sample provenance report, or browse all ReviewProof guides.