CompanyCam Photos Not Uploading? Preserve the Queue First

The short answer

If CompanyCam photos are not uploading, keep the original device intact and record what is pending before changing settings. First distinguish an upload queue problem from missing project access, an incomplete camera-roll import, or photos that already reached CompanyCam but not another system. Saving local copies is a precaution, not proof of a complete backup or successful recovery.

Do not clear app data, uninstall, reset the device or intentionally sign out while unresolved media remains. Keep the original item references and avoid deleting suspected duplicates during the incident. This is a documentation-based checklist with original proposed exercises; no device, account or recovery was tested.

Preserve the queue before choosing a fix

Record the device owner, app and operating-system versions, intended project, observation time and pending count. List the individual items, not just the total. Use harmless descriptions and private evidence references so you can compare the same files after one authorized change. A thumbnail is not a complete-file check.

CompanyCam's mobile troubleshooting guide describes Save All or individual local saving, and Retry All or individual retry. It advises keeping the app open during upload and warns that deleting the app loses unsynced media. Local saving is salvage to inspect, not proof that every file or its context is preserved. This guide does not turn the vendor's later logout or reinstall sequence into instructions: retain unresolved items and escalate to Support.

If a saved copy is available, record its specific location and check whether that individual file opens. Keep capture date, location, notes, annotations and attribution marked unchecked until reviewed. A working local image does not establish a complete backup of the project record.

Choose the branch that matches the evidence

CompanyCam's offline-mode guide says mobile media queues until reconnection, while cached projects cover a limited recent, starred or assigned set. Do not assume every project is available offline, or that a restored connection proves every item completed.

Permission-role documentation describes Restricted users' limited project access. A role change can remove access even to a project the person previously created while Standard. Have the authorized Admin or Manager review the intended assignment; broad access or a shared administrator login is not this protocol's fix.

CompanyCam's individual-login guidance warns that signing in elsewhere or shared logins can disrupt sessions and pending work. Keep the incident with the original device and responsible user rather than cycling sessions or sharing credentials.

Keep connection and import checks narrow

Apple's Low Data Mode guide says the setting is separate for cellular and Wi-Fi and limits background network activity and Background App Refresh. On an Apple device, record the active network and actual setting. It is a possible check, not a universal diagnosis. Consider only an appropriate authorized change, including potential data cost; this source does not establish Android controls.

CompanyCam's existing-media guide identifies photo-library permission, a Magic Uploader selection of up to 100 photos at a time and separate or manual selection for remaining images. It uses EXIF date when present, otherwise upload date. Manual re-upload does not establish restoration of annotations, attribution, original context or every metadata field, and does not prove automatic deduplication.

Before any additional upload, compare the intended project and file references with what already exists. Leave uncertain duplicates in the exception record rather than deleting them during troubleshooting. Make one authorized change with a reason and time, then compare the same items. If the error changes, preserve both observations instead of treating a different message as success.

Copy the missing-photo exception register

Use one row of this two-column record per item or a linked item list. It is an editorial working aid, not a CompanyCam feature. Keep photos, addresses, private project links and customer data in authorized records, not public support comments.

A lower queue count is only a changed count. Closure requires the specific files to visibly open in the intended project and important context to be checked. Keep an unexplained item unresolved even if other photos arrive. Downstream delivery and public sharing are separate decisions.

Three fictional exercises, not recovery results

Escalate without putting the photos at risk

Give Support the app and OS versions, device context, private project reference, exact error, timestamps, pending count, affected item references and changes already attempted. Explain which saved copies open and which context fields remain unchecked. Keep originals intact while the unresolved branch is reviewed.

If the photos already exist in CompanyCam but not Jobber, use the CompanyCam and Jobber destination protocol; this guide makes no video-support claim for that integration. Recovery does not authorize sharing, so public copies belong in the job-photo approval workflow. The offline software guide covers broader product evaluation. Here, finish with accounted-for items and visible exceptions, not a promised restoration.

Sources and evidence

Official documentation reviewed through the verified research handoff on 9 October 2026. Links near claims identify their source. The worksheet, decisions and fictional exercises are original editorial suggestions, not observed product results.

• CompanyCam mobile upload troubleshooting
• CompanyCam offline mode
• CompanyCam permission roles
• Uploading existing photos and videos
• Apple Low Data Mode
• Why each person needs their own CompanyCam login