For data safety reasons, we highly recommend always backing up the whole card, even if it contains irrelevant or old data that may waste time or storage space.
However, o/PARASHOOT does allow you to optionally ignore specific auxiliary file types during backup verification if you're certain they're not needed.
Available File Types to Ignore
You can choose to ignore the following file types:
Extension | Description |
| Low-resolution video files created by GoPro cameras |
| Thumbnail image files created by GoPro cameras |
| Camera metadata database files (e.g., for thumbnails, previews) |
| Camera settings save files (temporary configuration files) |
| Temporary backup copies created during settings changes |
| Internet shortcut files |
| Plain text files |
| Media Hash List files used for media file verification |
| Binary data files (camera firmware, configuration data) |
| XML metadata files (camera settings, EXIF data) |
How to Enable Ignored File Types
You can configure which file types to ignore in the Settings under Ignore File Extensions. Toggle on any extensions you want to exclude from backup checks.
These settings are also available via the CLI using the --ignore-extensions flag.
Common Use Cases
GoPro Workflows
GoPro cameras create .lrv (low-resolution video) and .thm (thumbnail) files alongside your main video files. These files are used for quick preview and playback on the camera itself. If you only back up the high-resolution .mp4 footage and don't need the preview files, you can safely ignore .lrv and .thm file types to speed up verification and save storage space.
Generic Camera Workflows
Many cameras create auxiliary files like .bin (firmware/configuration), .xml (metadata), or .db (database) files that you may intentionally exclude from your backup workflow. If you're certain these files aren't needed, you can ignore them to prevent verification errors.
How Verification Works with Ignored Files
When you enable ignored file extensions:
During backup verification, o/PARASHOOT will skip checking any files with the ignored extensions
You'll get ONE verification check before erasure that checks all non-ignored files at once
There won't be multiple error prompts - if files are missing, you'll see one message listing what's missing
Ignored files won't cause errors even if they're not backed up anywhere
Example: If you ignore .lrv and .thm files, and your GoPro card contains:
GH010234.MP4(main video file)GH010234.LRV(low-res preview)GH010234.THM(thumbnail)
Only the .MP4 file will be checked during verification. The .LRV and .THM files will be completely ignored, and you won't see any errors about them being missing from your backups.
Why Custom Ignores Aren't Supported
For data safety reasons, you cannot define your own file types to ignore. This limitation exists to protect you from accidentally excluding critical files from your backups.
It's surprisingly easy to make a mistake when specifying file patterns. For example, you might accidentally:
Ignore an entire category of important files (e.g.,
.movwhen you meant.lrv)Use a pattern that matches more files than intended
Exclude files you didn't realize were essential for your workflow
The whitelisted file types shown above have been carefully vetted to ensure they are truly auxiliary files that can be safely excluded without risking data loss.
Need to ignore a different file type? If you're confident that a specific file extension can be safely ignored without any risk to your backup integrity, please contact us via the chat icon. We'll evaluate your request and, if appropriate, add it to the whitelist in a future update.