Once safe, check the exact camera model and its retention setting before changing power or removing storage. Follow its save and transfer instructions, preserve the relevant sequence and open the copied files from their destination. Keep a separate backup and a short index of filenames, views, time discrepancies and delivery.
What you can do with this guide
- Check the exact model before unplugging or removing media; retention settings differ.
- Preserve the relevant sequence and verify a separate playable backup.
- Give the reviewer original filenames, useful playback positions and honest limits.
You can see the moment of impact on the screen. It is tempting to send that short clip and move on. First, make sure you have the recording—not just a thumbnail, a temporary file or a phone app that is still reading from the camera.
Preserve the sequence before preparing the highlight. The approach, impact and aftermath may sit in different files or camera views. Save the relevant available material using your model's instructions, then verify a separate copy that opens without relying on the camera.
There is no safe universal rule to unplug every dashcam immediately: some retention settings delete unsaved video at power-off. This guide covers recordings you own or may access, with clearly identified Garmin and Nextbase examples, a decision tree and a copy-verification worksheet.
First establish safety, the device and the recording's location
Do not stay in traffic, enter a damaged vehicle or delay emergency care to operate a camera. The NAIC's collision guidance puts safety first and says to call 911 when someone is injured. A useful recording is not a reason to take a physical risk.
Once safe, identify the camera's make and exact model from its label, existing app information or purchase record. Note the app name too. A tutorial for another model may show a button or storage behavior yours does not have. For a built-in vehicle camera, use the vehicle manufacturer's instructions for that system.
Write down what you actually know before changing anything:
- Is the camera currently on, off or inaccessible?
- Did you press a save/protect control, or only see an incident alert?
- Are you viewing a recording stored on the camera, or a file downloaded to the phone?
- Is there a rear or cabin camera, and was it connected?
- Do you know the retention setting and the approximate collision time?
If the vehicle has been towed, arrange authorized access through its custodian. Ask about the camera and removable media without assuming a storage-yard employee knows how your model works. Our tow-yard guide addresses the separate access, storage and release questions.
Use this decision tree before choosing a transfer method
Find the row that describes the evidence you have, not the status you hope the device created. Several rows can apply at once. Record unresolved questions instead of repeatedly changing settings to see what happens.
On a phone, swipe across the table to see all columns.
| What you have | Next useful action | What remains unconfirmed |
|---|---|---|
| A safe, operating camera with a recent event | Consult the exact model's save/protect instructions and retention behavior promptly. Locate the relevant sequence when the supported controls allow it. | Whether the event and its surrounding context were saved. |
| A clip marked saved or protected | Identify its filename and interval. Plan a separate copy using the manufacturer's supported route. | Whether other segments or camera views are needed, and whether an independent copy exists. |
| A clip visible only inside an app | Determine whether the app is browsing the camera or holding a local download. Preserve existing app files before reinstalling or migrating. | Whether you can open the complete recording independently of the camera connection. |
| Files copied to another device | Open that destination folder, review the copied files and complete the worksheet below. | Whether the files cover the intended sequence and whether another backup exists. |
| A damaged device, unreadable card or unexplained missing files | Record the condition and error. Seek model-specific support or qualified recovery help before destructive troubleshooting. | Whether a recording exists or can be recovered at all. |
A filename, thumbnail or completed progress bar answers only part of the question. Your verification should end at the destination copy, with playback and a record of the interval preserved.

Garmin X110 example: power-off can delete unsaved footage
The Garmin Dash Cam X110 camera-settings page distinguishes two retention options. Delete When Full replaces the oldest unsaved video when storage fills. Promptly Delete removes unsaved footage more than three minutes old and deletes all unsaved footage whenever the device powers off. The same page warns that formatting removes the card's videos and data.
That is why a generic “unplug it first” checklist is unreliable. For this model, identify the active setting and use the appropriate saving instructions while it is safe to do so. Do not change the setting and assume previously deleted footage will return.
The X110's saving instructions describe a default incident-sensor recording covering 15 seconds before and 15 seconds after a detected event, plus manual saving with the save control. Garmin also recommends transferring saved recordings because card storage is limited. These are X110 instructions, not the operating sequence for every Garmin or another brand.
Nextbase 322GW example: protected is not a permanent backup
Nextbase's protection guidance for the 322GW, 422GW, 522GW and 622GW explains manual protection and G-sensor triggers. Its one-minute-segment example protects different neighboring files depending on when the trigger occurs. A protected clip therefore does not establish that you have every useful part of the approach and aftermath.
The page identifies FH/FL as front high-/low-definition versions and RH/RL as rear versions. Inspect the files actually present; a rear filename is not something to assume when no rear camera recorded. The page also tells owners with missing clips to consider the protected-space limit and to back up important recordings. Do not treat the protected label as indefinite retention.
For your own file list, identify the approach, collision and immediate aftermath, then check for gaps between segments. Preserve the relevant available originals and their view/quality variants before selecting a shorter viewing copy. This organizational step does not require guessing a universal number of minutes that every camera retains.
Make a separate copy using the route for your model
Create a clearly named destination folder, such as “Collision 2026-10-29 — camera copies.” Copy rather than move the relevant files when the supported interface permits it. Retain the camera's filenames inside that folder and put your explanations in a separate note. Avoid trimming, relabeling timestamps or adding captions to the preservation copies.
Garmin X110 computer route: Garmin's computer-file instructions place recordings in DCIM. It identifies 100EVENT for automatically saved incidents, 102SAVED for manual saves and 105UNSVD for unsaved footage. These folders are useful search locations, not proof a particular incident was recorded. Check retention behavior before any step that changes power or removes media.
Nextbase Series 2 route, including 322GW: the current retrieval instructions describe a computer USB connection to the camera body, not the mount, selecting Mass Storage or Access files, and copying from DCIM. They also describe a separate card-reader method that requires the camera to be powered off before card removal. Apply that sequence only to the applicable equipment; it is not a substitute for the Garmin retention check above.
The Nextbase support article also contains general troubleshooting advice involving resets and formatting. Those are not the preservation steps recommended here when an important recording may exist only on that device. Stop at copying and verification; a procedure for restoring ordinary equipment operation is a different task.
If using a phone, distinguish an export from a source-file copy. Garmin's X110 export page describes trimming, an audio-inclusion option and a completed-export choice to save to the phone. It separately offers removal from the camera. Note which process you used and retain a full source recording when available, rather than treating a shortened export as the only record.

Check existing phone files before changing apps
An app problem can become a file-loss problem if the only downloaded copy is inside the app you delete. First list what is on the camera, what is downloaded and what is already copied elsewhere. Do not use an app thumbnail as your backup inventory.
For a current, specific example, Nextbase's September 2026 migration instructions distinguish moving existing footage from MyNextbase Connect to the Nextbase App from starting fresh. The start-fresh route deletes the old app and loses its saved files. The preservation route includes copying the data and waiting for completion.
If this applies to you, verify an independent copy before starting maintenance. If you already changed apps, record what you did and when; do not assume that either an empty new library or a remembered old thumbnail establishes the recording's present location.
Use a copy-verification worksheet
Open files from the destination folder, not from a camera gallery that may still be connected. Check the beginning, the incident and the end of each relevant segment. Then review the sequence across file boundaries. Where playback is possible, confirm the expected view and whether audio is present; silence alone does not tell you why audio is absent.
Make a second independent backup in storage you control, keeping access limited. Two folders on the same device do not protect against losing that device. If a cloud service is involved, confirm the upload finished and that you can retrieve and open the files. Keep the original source available when safe and practicable; a checked copy is not a reason to erase it immediately.
On a phone, swipe across the table to see all columns.
| Record | What to enter or check | Uncertainty to preserve |
|---|---|---|
| Source | Exact camera model, card or app location, and who performed the copy. | Unknown firmware, settings or prior handling. |
| Files and view | Original filenames, front/rear/cabin view if identifiable, file count and displayed sizes. | Unidentified quality variants or missing expected files. |
| Time coverage | Displayed start/end times and what portion of the sequence each file shows. | Gaps, an incorrect camera clock or unclear time zone. |
| Transfer | Date, method, destination and whether it was a file copy or an app export. | Trimming, audio choices or other export changes, if any. |
| Playback | Which destination files opened; whether the beginning, event and end played. | Errors, freezes, a missing view or unexplained silence. |
| Backup and delivery | Second-copy location; later recipient, files supplied and acknowledgment. | A pending upload or receipt that does not confirm the files opened. |
A matching filename or size is a useful inventory check, not proof of authenticity or a forensic comparison. This worksheet records your ordinary preservation work. It does not certify that a file is unaltered, settle fault or guarantee that a court will admit it.
Make a video packet someone else can actually review
Once preservation copies are safe, prepare a small index for the person receiving them. You should not have to send a full memory card with no explanation or rely on a heavily edited clip to communicate the point.
- Identify the sequence: List the original filenames in viewing order, including the relevant approach and aftermath when available.
- Identify the view: Front, rear or cabin; note a blocked view or a disconnected camera rather than assuming it recorded.
- Point to the relevant moment: Give the approximate playback position within the file, separately from any clock printed in the image.
- Explain known limits: Missing segments, absent audio, an uncertain clock setting or a transfer error belong in the note.
- Keep delivery clear: Name the files uploaded, date sent and receipt. Ask whether the recipient could open the material.
Illustrative index entry: “Front camera, file [original name]. The vehicle enters the junction around 00:18. The file before it contains the approach. The overlay clock differs from my contemporaneous note by about one hour; the reason is not confirmed.” This points the reviewer to the material without presenting your explanation as a technical conclusion.
If a recipient wants a short clip, keep that excerpt separate from the full preserved files. Label its source and any trimming, audio removal or conversion. A useful viewing copy can coexist with the complete material; it should not replace it.
If responsibility is disputed and the accident caused injuries, learn about a free injury case review. Bring the file index and available recordings, along with the precise dispute. No single clip automatically establishes a payout, but a clear handoff lets the relevant questions be examined.

Record time discrepancies without rewriting the recording
Keep three things separate: the time displayed within the recording, the file information shown by your device, and the collision time you recorded from another source. If they differ, describe the difference. Do not change an original to make all three agree.
A useful note might read: “The video overlay shows 16:12. My contemporaneous note records approximately 17:12 local time. I have not established whether the camera clock or time-zone setting explains the difference.” That is clearer than silently renaming the recording with a supposedly corrected exact time.
Add context that someone viewing the files cannot obtain from a filename alone: the road and direction, which vehicle carried the camera, where it was mounted, the sequence of filenames and any view obstruction you observed. Distinguish your recollection from what the image actually shows.
If a police report is available, keep it as a separate record. Our guides explain how to obtain the correct crash report and how to request a factual correction. Do not edit the video simply to make it match a disputed report entry.
Example: a saved clip and a verified record are different
Fictional preservation example: Jordan owns a Nextbase 322GW with a rear camera. After reaching a safe location, Jordan sees a protected front clip. This example illustrates file organization, not a real client's accident or result.
Jordan checks the model's instructions and uses the supported USB transfer route. The file list contains front and rear recordings, with more than one quality version. Instead of sending the first small file that opens, Jordan copies the relevant sequence into a dated folder and keeps the filenames.
Playback from the copied folder shows that the protected front clip starts after the vehicle has already entered the junction. A neighboring available segment contains the approach. Jordan includes that segment and checks the corresponding rear view. The worksheet names the files reviewed and records what each covers, without claiming that protection automatically saved everything.
The overlay time differs from Jordan's notes. Jordan preserves both and records the unresolved discrepancy. A second copy is verified on separate storage. For the insurer, Jordan provides the requested files through the confirmed upload route, with a short index explaining the sequence and time issue.
The upload confirmation is retained. Jordan then asks whether the recipient can open the files and whether another format or segment is needed. None of those steps establishes who was at fault or how much a claim is worth. They make the material and its limits easier to examine.
Deliver a usable copy and keep a delivery record
Ask the intended recipient for its verified upload route, accepted formats and size limits. If a shorter clip is requested, keep it separate from your preservation copies and label it as an excerpt with its source filenames. Explain any missing audio or other deliberate export choice. A recording of your phone playing the clip is a new recording, not the camera's source file.
Record what you supplied, to whom, when and by which method. An acknowledgment of upload is different from confirmation that the files can be opened or have been reviewed. If an insurer says footage is missing, identify the exact file, submission date and receipt before resending. The pending-documents guide helps separate a delivery problem from a claim decision.
Before public posting, consider the private conversations, passengers and identifying details captured. Ask for individual advice if recording, disclosure or a legal request raises privacy concerns. Preserve the source and obtain guidance about any redacted sharing copy; this guide does not decide the rules governing a particular recording.
If footage is missing, stop guessing what the device did
List the locations actually checked, the approximate time sought and the exact error or empty folder observed. Preserve any existing phone or computer copies. An incident notification does not prove a playable file survived, and an empty app view does not prove every other storage location is empty.
For damaged equipment or unreadable media, describe the condition to the manufacturer or a qualified recovery specialist before permitting work. Make clear that preserving a possible recording is the priority. Ask what the proposed procedure would change, whether it could overwrite data and whether they can proceed without destructive steps. Recovery is not guaranteed.
Finish the handoff with the file index, preservation notes, available copies and unanswered questions. Identify what exists, what has been checked and what remains uncertain. Keep the original material available so a short viewing copy never becomes the only account of what the camera recorded.
Your next step
You have footage. Get clear about the injury-claim questions.
If the collision left you injured and responsibility or a settlement is disputed, prepare the original sequence and your open questions for a free case review. Keep the recordings private and share them through the provider’s verified process.
See My Injury Case-Review Options →Free initial review through an independent provider. No obligation to hire.Sources and scope
Core sources checked October 29, 2026; editorial update October 31, 2026. State examples apply only to the named jurisdiction. This guide is editorially researched; it has not been reviewed by an attorney and does not assess your individual claim.
- Garmin Dash Cam X110: Camera Settings
- Garmin Dash Cam X110: Saving a Video Recording
- Garmin Dash Cam X110: Videos on Your Computer
- Garmin Dash Cam X110: Editing and Exporting a Video
- Nextbase: File Protection — 322GW, 422GW, 522GW and 622GW
- Nextbase: Retrieve, View and Troubleshoot Series 2 Footage
- Nextbase: Switching from MyNextbase Connect to the Nextbase App
- NAIC: What You Should Know About Filing an Auto Claim
Spot an error? Contact support@injurylawadvisor.us with the page and source. Please do not email medical records or sensitive case details.



