How to export your photos from autofox (and move to VehiclePhoto)

Collect the destination copies that already represent the finished gallery, join them to your untouched photographs, and verify coverage before disconnecting anything. autofox publicly describes automatic delivery into a DMS, IMS, or website, making those destination systems the confirmed place to recover processed images.

Ownership

What you own

autofox does not state this publicly

Request written confirmation that you may keep and reuse both uploaded originals and processed images after cancellation. Also ask whether autofox can provide a direct full-resolution archive that is separate from copies synchronized to outside systems.

Export

Get your images

autofox says processed images are automatically transferred to a DMS, IMS, or website by direct API integration or multi-platform FTP synchronization. Its public page does not supply a separate download sequence, so use the receiving system’s copy as the verified export path.

1. Export the received images. Locate each processed image in the receiving DMS, IMS, or website, then use that destination’s controls to export or download the stored copy. Preserve its vehicle association and compare the recovered count with the live gallery. Source

VehiclePhoto

Move into VehiclePhoto

Start from the richest copy available across the receiving systems. Compare resolution and compression before choosing duplicates, keep an untouched backup, and group the winners by vehicle and view. A controlled sample in VehiclePhoto then establishes the new background, framing, blur, and brand choices.

1. Bulk uploader. Open a listing, then drag and drop the image set into the bulk uploader. Individual images and folders can enter together, and the original files remain untouched.
2. ZIP uploader. Choose a ZIP archive when the export arrives as one package. The uploader expands supported image files so you can check the listing before processing begins.
3. REST API v1 ingest. For files already hosted at HTTPS URLs, send each URL to /api/v1/ingest with a REST API v1 key instead of downloading and uploading it by hand.
4. Phone-capture QR handoff. When a missing angle needs a new photo, open phone capture on a computer and scan its QR handoff. The phone adds that image to the same work without a separate app.

Migration boundary

What carries over

Nothing automatic — there is no autofox connector. Recovered files can move, while capture guidance, delivery mappings, FTP or API configuration, application state, processing history, and account settings remain separate. VehiclePhoto exports completed work for you to deliver; direct DMS push is not live.

Final check

Before you cancel

• List every receiving system named in the current setup and identify which one holds the best copy. autofox documents DMS, IMS, and website delivery through API or FTP synchronization. Source
• Do not treat a public webpage image as the archive until its pixel dimensions are checked. A display layer may serve a smaller derivative than the file stored inside the receiving system.
• Ask autofox for ownership, processed-output rights, retention, and full-resolution export details in writing before you cancel.
• Save a mapping of vehicle identifiers to filenames before integrations are removed. FTP paths or destination records may contain the relationship that bare images no longer reveal.
• Compare one rebuilt VehiclePhoto gallery with the still-live destination copy. Check ordering, edge quality, logo placement, and all privacy masks before scaling the move.

References

Sources

• www.autofox.ai — Documents automatic processed-image delivery to a DMS, IMS, or website through API or FTP.

More switching guides