You have the clip. The other driver's insurer has already read it and responded with: "This footage is insufficient to establish liability." That sentence appears in thousands of claim files every year, and it is almost never about what the camera captured. It is about how the footage was handled, exported, timed, and presented.
Adjusters work under fraud pressure and state insurance regulation. A raw MP4 on your phone screen proves nothing to them because it can be trimmed, sped up, or re-encoded. What moves a file from "interesting video" to "evidence we will pay on" is a small set of repeatable habits that take twenty minutes to set up once and five minutes per incident afterwards.
RedTiger cameras store footage in DCIM folders on the microSD card, typically with filenames containing the model prefix and a timestamp. Those original files carry the firmware's own datetime stamp inside the container metadata, which is why they are far more persuasive than anything you export.
The most common way good footage gets thrown out: the camera clock is wrong. If the overlay reads a date three weeks old, the opposing adjuster will argue the clip is from a different incident, and you cannot easily prove otherwise. RedTiger cameras sync time through the app over WiFi, or manually in Settings → Date/Time. GPS-equipped models also update the clock from satellite time on boot, but only after the GPS module has a fix — which can take several minutes the first time.
Check the overlay on your first drive of every month against your phone's clock. It takes ten seconds and it is the difference between a claim that settles in eleven days and one that drags through arbitration.
Every insurer has its own portal, but they all want the same six things. Deliver them in one folder and you cut weeks of back-and-forth:
| Item | What It Should Contain | Why It Matters |
|---|---|---|
| Original clip(s) | Front and rear, unedited MP4 or MOV, full folder | Preserves firmware metadata and continuity |
| Hash list | SHA-256 for each file, in a dated text file | Demonstrates files were not altered after export |
| Incident statement | One page: time, location, direction of travel, what happened | Lets the adjuster match footage to the loss report |
| Camera details | Model, serial number, mount position, resolution setting | Establishes field of view and reliability |
| Photo of the mount | Where the camera sits, with the windshield in frame | Confirms footage was captured from your vehicle |
| Screenshot of the timestamp | The overlay showing date and time, plus your phone clock | Pre-empts the "clock was wrong" objection |
Name the folder with the date and claim number: 2026-03-14_CLAIM-884219. Adjusters handle hundreds of files weekly; anything named "VID_0031" gets pushed to the bottom of the queue.
Insurers cannot always open HEVC or high-bitrate 4K files, especially on older internal systems. If you must transcode, keep the original and hand over both. Use H.264 MP4 at the original frame rate and bitrate — do not reduce frame rate, because frame rate is used to calculate speed. A clip cut from 30fps to 15fps looks unnatural and invites a challenge.
Do not add music, do not add captions over the footage, do not zoom digitally. If you want to highlight something, produce a second "annotation copy" clearly labelled as a derivative and keep it separate from the original set. Mixing a derivative with originals is how footage gets accused of manipulation.
Most small claims do not need a formal chain of custody, but they do need a credible story. Write down, in one short paragraph, where the card has been since the incident: stayed in the camera until the 14th, then removed and copied to a laptop, then the card was returned to the camera and formatted on the 20th. Note who had access. If the file is going to court rather than an insurer, keep the card unformatted and hand over a copy on a fresh drive instead.
Be careful not to oversell what you have. A dash cam establishes your direction, your speed at the moment of impact, and the other vehicle's position. It does not prove the other driver's insurance status, and it does not — by itself — establish fault in every jurisdiction. In rear-end collisions it is close to decisive. In intersection disputes with amber lights, the adjuster may still split liability.
Where footage reliably earns its keep is in these situations: rear-end hits where the other driver claims you braked abruptly, lane-change sideswipes, parking lot damage, staged accidents, and any case where the other party's story contradicts physics. Rideshare and delivery drivers get the highest return, because passenger disputes and unreported contact damage are otherwise almost impossible to evidence.
If you are setting up a car for this purpose, a dual-channel kit is the practical minimum — the RedTiger 4K front and rear setup covers the rear-end claims that front-only cameras miss entirely, and the rear channel is where most disputed collisions actually are.
That last step matters more than people expect. Telling an insurer in writing that unedited, hash-verified footage exists changes how a claim is triaged before anyone has even watched it.
← Back to Blog