What we accept
The browser uploader takes JPG, JPEG, PNG, WEBP, and GIF images.
The Compressor app takes JPEG, PNG, and WebP images plus most video formats — it pulls the individual frames out of video on your computer and uploads those as photos.
Neither accepts HEIC. If your files are HEIC, convert them to JPEG first or change your camera’s setting.
Timestamps are the important part
Everything in your report is a time. When feed arrived, how long the bunk was empty, how far a delivery drifted from your usual hour — none of it means anything without an accurate time on every photo.
We get that time from two places:
- The information stored inside the photo file by the camera when it took the shot. This is the primary source, and the Compressor preserves it exactly when it shrinks your photos.
- The timestamp printed on the image — the date and time your camera burns into the corner of the picture. This is the backstop for when the stored information is missing or unreadable.
That is why the timestamp overlay setting is not optional. See Camera requirements and settings.
Set the camera clock, every time
If your camera’s clock is wrong, every event in your report is wrong by exactly the same amount, and nothing we do afterwards can fix it.
Two specific traps:
- Battery changes reset the clock on many trail cameras — often back to a factory date years in the past.
- Daylight saving shifts mid-run will show up as your whole routine jumping an hour.
Check the clock before every run, and use 24-hour format.
If the dates are far out, we may not be able to build a usable report at all. A camera whose clock says the photos were taken a year ago produces a report with no events in it — see If your report has no events.
Photos from more than one camera
Keep them separate. One project, one barn, one camera position. Mixing footage from two cameras into one batch gives you a report that describes neither of them, because the bunk outline you draw only fits one of the views.
Duplicates
You do not need to worry about them. If a file has already been uploaded successfully, it is detected and skipped rather than counted twice. This is what makes re-uploading a failed batch safe — see Resume or re-upload a batch.