Which devices and browsers are supported?

Mobile: iOS Safari and Android Chrome are the primary targets and receive the most testing, since the overwhelming majority of captures happen on a phone.

Desktop: Chrome, Edge, Firefox, and Safari all support live sessions and screen sharing.

The customer can switch between front and rear cameras mid-session, which matters constantly in field work where the rear camera does the real job.

Portrait and landscape are both handled, with an on-screen orientation indicator so a guided step can ask for the framing it actually needs.

Where a device cannot support live capture — an old browser, a locked-down corporate device — the flow degrades to a verified upload path so the inspection can still be completed.

Verification checks still run server-side on uploaded files.

The workspace at virtualinspection.ai/app installs as a progressive web app on phones and tablets, giving inspectors a home-screen icon and better offline tolerance in the field.

Virtual Inspection Pro supports iOS Safari, Android Chrome, and desktop Chrome, Edge, Firefox, and Safari—modern browsers with camera access. Older devices fall back to a simplified upload flow. For an iOS Safari inspection, use an iPhone or iPad that can clearly show the required details. For an Android Chrome inspection, check that the camera can focus on labels, connections, and other close-up evidence before the appointment.

Browser support is only one part of readiness. A laptop may suit a stationary discussion, while a phone is usually easier to position around a property. Inspectors and property teams should choose equipment based on what must be shown, not just whether a page opens. Keep browsers updated under your organization’s IT policy. The supported-browser list does not establish a minimum operating-system version or guarantee performance on every device configuration.

Before the scheduled inspection, open the inspection page in a supported browser and respond to its camera-permission request. If access was previously denied, check the browser’s site permissions and the device’s privacy settings, then retry. W3C’s Media Capture and Streams specification describes browser-based camera access as permission-controlled and restricted to secure contexts. A compatible browser therefore does not override a user’s denial or an administrator’s restrictions.

For an agency-managed tablet or corporate laptop, ask IT to investigate restrictions rather than trying to bypass them. If the camera remains unavailable, close other applications that may be using it and test again. Also check battery charge, lighting, lens cleanliness, and connectivity at the actual inspection location. A successful test at a front desk may not reveal a weak connection in a basement or mechanical room. Complete these checks early enough to arrange another device if necessary.

The simplified upload flow provides a fallback for older devices; it should not be treated as proof that every inspection requirement can be met through uploaded material. Before relying on that route, ask the responsible inspector or reviewer which views, identifying details, and context are needed. Establish a separate contingency for connection failures or permission problems rather than assuming that every failure automatically triggers the older-device fallback.

For example, a property manager may use an older phone to submit images of a repaired water-heater installation. The reviewer may be able to read the equipment label but still lack a clear view of a connection behind the unit. The appropriate next step is to request additional evidence or arrange a visit—not infer that an unseen condition is satisfactory. Keep a simple record of what was requested, what could not be shown, and who decided the next action.

Government agencies should define which inspection types are suitable for remote review before publishing device instructions. ICC’s remote virtual inspection guidance is relevant to that planning: browser compatibility alone does not determine whether a particular inspection should proceed remotely. Appointment instructions should name the supported browsers, explain camera permissions, identify the required views, and give participants a contact route when technical checks fail.

Use human review whenever images are ambiguous, the location or subject cannot be confidently identified, or required details are missing. Arrange an in-person visit when the task requires physical testing, concealed areas cannot be adequately assessed, or safe camera positioning is not possible. Never ask a participant to climb, remove protective covers, or enter a hazardous area merely to obtain a better view. Technical access enables participation; the authorized reviewer remains responsible for deciding whether the available evidence is sufficient.