Building an Insurance Claim Evidence Pack: Photos, Policy Pages, and Correspondence in One PDF

TL;DR

An insurance claim is won or lost on documentation, and the single most common self-inflicted wound is sending twenty loose files by email. Attachments get separated from the thread. Phone photos arrive as 8MB each and bounce off a size limit. The adjuster's system indexes one document per claim and yours arrives as fourteen.

One ordered PDF fixes most of that. Damage photos, the policy wording as it stood, receipts, correspondence — in the order that tells the story, with a contents page at the front.

Convert: Anything to PDF merges images and documents into a single PDF entirely on your machine — no upload, no watermark, no size cap. Convert: Web to PDF captures the online pieces: your policy page inside the insurer's portal, the claim status screen, the retailer's product page proving what the item cost.

The privacy point isn't decorative here. A claim file contains your address, your policy number, photographs of the inside of your home, and sometimes medical or financial detail. Local conversion means none of that touches a third-party server on its way to becoming a PDF.

General guidance, not insurance or legal advice — your policy and your regulator's rules govern.

Why one file beats twenty

Talk to anyone who handles claims and the complaints are consistent:

• Attachments get orphaned. Email threads get forwarded, split, and re-filed. The photos end up in a different place from the description of what they show.
• Size limits truncate submissions. Portal uploads commonly cap at 10–25MB total. Modern phone photos are 3–8MB each. Six photos and you're over.
• Order carries meaning. "Before, after, close-up of the serial number, receipt" is an argument. The same four files in alphabetical order by camera filename is not.
• Nothing is labelled. IMG_4471.HEIC tells the adjuster nothing. A page with the photo and a caption underneath tells them everything.
• Web pages vanish. The product listing that proves the item's replacement cost gets delisted. The policy page gets rewritten.

A single PDF with a logical order and a contents page addresses all five, and it takes about twenty minutes.

What goes in the pack

Assemble in this order. It's the order that reads as a narrative rather than a pile.

1. Cover page and contents

One page: your name, policy number, claim reference if you have one, date of loss, date of submission, and a numbered list of what's inside with page numbers.

Write it in any text editor, save as .txt or Markdown, and convert. It takes four minutes and it's the page the adjuster will actually use to navigate.

2. The policy as it stood

Capture your policy documents and — importantly — the policy summary page inside the insurer's own portal, showing your coverage, limits, and excess as of today.

This matters because portal pages change. Coverage gets updated at renewal, and the page reflects current state, not state at the date of loss. Capturing it now at least pins down what you were being shown while the claim was live.

Convert: Web to PDF handles this: it converts the page rendered in your browser, so a logged-in policy page converts normally. A URL-based converter can't — it fetches the address from its own servers with no session and gets a login screen.

Turn on Chrome's print headers and footers so the URL and capture date are stamped on the page. For anything archival, that stamp is what makes the document useful later.

3. Proof of ownership and value

• Original purchase receipts (email receipts convert directly from the browser)
• Bank or card statement lines showing the purchase
• The retailer's current product page, for replacement cost
• Warranty registration confirmations
• Photos of the item in use before the loss

On the retailer page: capture it now. Product pages get delisted and prices change, and "it cost about £900" is a much weaker statement than a dated PDF of the listing.

4. Damage documentation

The most important section, and the one people rush.

Take more photos than you think you need, in a deliberate sequence:

• Wide — the whole room or the whole vehicle, establishing context
• Medium — the damaged item in its setting
• Close — the specific damage, filling the frame
• Identifying — serial number, model plate, VIN, meter reading
• Scale — something of known size next to the damage where scale is ambiguous

Photograph in daylight where possible, and don't clean up first. Adjusters read a tidied scene as a compromised one.

Keep the originals untouched somewhere separate. The originals carry EXIF metadata — capture timestamp, and often GPS coordinates — and that metadata corroborates when and where the photo was taken. Converting to PDF produces a document for the adjuster; it does not preserve EXIF, so archive the raw files alongside it.

That's a genuine limitation stated plainly: the PDF is the readable submission, not the forensic original.

5. The paper trail

Everything exchanged since the loss:

• Emails to and from the insurer
• Portal messages and claim status screens
• Notes of phone calls — date, time, who you spoke to, what was said, any reference number
• Police reports or incident numbers, if applicable
• Contractor or repairer estimates

Those phone-call notes are worth the effort. Write them the same day in a plain text file; a contemporaneous note is far more credible than a reconstruction three months later.

6. Third-party estimates and expert reports

Repair quotes, contractor assessments, engineer reports. Include the letterhead and contact details — an estimate the adjuster can't verify is an estimate they can discount.

Assembling it

Get the file sizes down first

This is the step people skip and then hit the upload cap.

Phone cameras produce 3–8MB images. Twenty of those is well past most portal limits. Before merging, resize your photos to something in the 1500–2500px range on the long edge — that's more than enough detail for any adjuster viewing on a screen, and it cuts file size by an order of magnitude.

Every OS does this without extra software: Preview on macOS (Tools → Adjust Size), Photos on Windows, or any image editor.

Handle iPhone HEIC files

If your photos are .HEIC, convert them to JPG first — HEIC support in insurance portals is inconsistent, and a file the adjuster can't open is worse than no file. macOS and Windows both convert HEIC natively now; we've written up the Windows route separately.

Merge in order

Convert: Anything to PDF takes multiple files and produces one PDF. Two things that make the output much better:

Name files so they sort correctly. 01-cover.txt, 02-policy.pdf, 03-receipt.jpg, 04-damage-wide.jpg. Alphabetical sort then equals your intended order, and you're not fighting the tool.

Choose orientation deliberately. Portrait for documents and text, landscape for wide photos and estimates with tables. If most of your pack is landscape photos, converting the whole thing landscape reads much better than portrait pages with letterboxed images.

Everything happens on your machine. No file is uploaded, which for a document containing your address, policy number, and photographs of your home's interior is the entire point.

Check the final file

Before sending: open it, page through it, confirm the order matches the contents page, and check the file size against the portal's stated limit. If you're over, resize the photos further rather than removing them.

Why not just use an online merge tool

The instinct is Smallpdf or iLovePDF. Consider what the pack contains before you upload it:

• Your full name and home address
• Policy and claim reference numbers
• Photographs of the inside of your home, including what's in it
• Purchase receipts showing your spending
• Sometimes medical detail, sometimes financial statements

Reputable services delete uploads after a retention window, and that's a real mitigation. It's still a copy of your household inventory on infrastructure you don't control, processed under terms you probably didn't read, for a task that doesn't require a server at all.

There's also a practical issue: free tiers cap file sizes and conversions per day, and an evidence pack is exactly the kind of large multi-file job that hits those caps.

Local conversion has no cap because there's no server metering it.

Claim-type quick reference

That last row is worth doing: a dated PDF of the meteorological record for the day of loss is easy to capture and pre-empts an obvious question.

Frequently asked questions

Should I send my insurer one PDF or separate files?

One ordered PDF with a contents page, unless your insurer's portal specifically asks for separate uploads by category. A single file stays together through forwarding and re-filing, keeps your intended order intact, and is far easier for an adjuster to work through than twenty attachments.

How do I get my photos under the portal's upload limit?

Resize before merging. Reduce images to roughly 1500–2500px on the long edge — plenty of detail for on-screen review — which typically cuts a 6MB phone photo to a few hundred kilobytes. Merge afterwards. Removing photos should be the last resort, not the first.

Can I capture my policy page if it's behind a login?

Yes, with a browser extension that converts locally. Convert: Web to PDF converts the page already rendered in your tab, so a logged-in policy or claim status page converts normally. URL-based converters fetch the address from their own servers without your session and will return a login screen instead.

Does converting photos to PDF preserve the timestamp metadata?

No. Converting produces a document, not a forensic copy — EXIF data including capture time and GPS is not carried into the PDF. Keep the original image files somewhere safe alongside the PDF. If your insurer asks for originals, send those.

Is it safe to use an online PDF merger for claim documents?

It's a choice worth making deliberately. Your pack contains your address, policy number, photographs of your home's interior, and often financial detail. Reputable services delete uploads after a retention period, but the files still pass through third-party infrastructure for a task that can be done entirely on your own machine. Local conversion avoids the question.

What if my photos are HEIC files from an iPhone?

Convert them to JPG before assembling the pack. HEIC support across insurance portals is inconsistent, and a file the adjuster can't open helps nobody. macOS and Windows both handle the conversion natively.

Will the PDF be accepted as evidence?

Insurers routinely accept PDF submissions, and a well-organised pack usually speeds a claim up rather than slowing it down. But a PDF you assembled is documentation, not a certified record — keep your original photos and correspondence, and follow whatever format your insurer's own claims process specifies. This is general guidance, not insurance or legal advice.

Bottom line

Claims are decided by people reading files under time pressure. Make the file easy to read and you've removed the most common reason for a follow-up request, which is the most common reason for a delay.

Capture the policy page and the retailer listing now, while they still say what they say. Photograph in a deliberate sequence — wide, medium, close, identifying. Resize before you merge. Number your filenames so the order is right. Put a contents page at the front.

And keep your originals. The PDF is the submission; the untouched files are the record.

Convert: Anything to PDF merges the pack locally with no uploads, no watermarks, and no size limits. Convert: Web to PDF captures the portal and retailer pages, including behind a login. Both are free.

And when the claim's finally settled and you want to do nothing for an evening: CineMan AI.