How to evaluate local-file APIs for a hardware inventory

You are preparing a hardware inventory and need to know whether its browser-based form can open or save local files. A browser may support some file features but not others, and a support report cannot confirm that a particular inventory app can complete its workflow.

Start with TooLab’s Browser Info to check the browser’s reported features. Then test the actual file-open or file-save task with a harmless sample on the computer and browser profile you plan to use.

Check local-file support

1. Open Browser Info on the computer where you will run the inventory. Check the browser version, permissions, privacy details, and supported features.
2. Look through the supported features for file access entries. Names may include File System Access API, file picker, or related file system features. Record what the browser reports, including the browser and version.
3. Write down what the inventory must do. Opening a CSV selected by the user, dragging in a file, saving a report, and reopening a saved project are different operations.
4. Try the real operation in the inventory app using a small, non-sensitive test file. If it asks you to choose a file or folder, select only the test item and note whether the app can read it or save a result.
5. Repeat the check in the exact browser profile and computer setup that staff will use. A managed work browser, private window, or different browser version may have different permissions or policies.

Do not use a real inventory export for the first test. A small sample with no names, serial numbers, or other private details is enough to confirm the basic workflow.

What the result means

A file access feature is reported as supported

The browser says it implements that feature. This is useful when comparing browsers, but it does not mean a website can search the computer, read every folder, or access files without your action. Modern browsers generally require you to choose a file or folder and may ask for permission.

A feature is missing or not reported

The browser may not support that particular API, or Browser Info may not report it separately. This does not automatically mean the inventory cannot accept a file. A basic file upload control, often labeled Choose file or similar by the app, can work without the newer File System Access API.

The app opens a selected file but cannot save back to it

Reading and writing are separate capabilities. Some workflows let an app read a file you selected, then download an edited copy rather than write directly to the original. Check whether that output is acceptable for your inventory process before deciding the browser is unsuitable.

The browser reports support, but the app still fails

The feature report describes the browser, not the app’s code, site permissions, or workplace policies. The app may use a different API than the one you checked, or a managed setting may block the request. Test the same file task in another approved browser to narrow down the cause.

How to fix a blocked file workflow

1. Use the app’s file picker. Choose a test file through the app’s own file-selection control instead of expecting it to find a file by its name or location. Browsers restrict websites from browsing local folders without user involvement.
2. Check the browser’s site permissions. Open the site’s controls from the icon beside the address bar and review any file or folder access permission shown there. Permission options vary by browser, and not every browser exposes the same controls.
3. Check operating-system privacy settings if access is denied. On Windows 11, review Settings › Privacy & security › File system. On macOS, review System Settings › Privacy & Security › Files & Folders. These settings can affect app access, but they do not replace choosing a file in the browser.
4. Try a normal browser window. Private browsing can limit stored permissions or behave differently from your usual profile. If the task works in a normal window, review the private window’s restrictions before relying on it for inventory work.
5. Check with your administrator. If the computer is managed, a browser policy or security product may restrict file pickers or access to particular folders. Ask the administrator before changing a managed setting or installing another browser.
6. Update the approved browser. If the feature is missing or the app fails only in an older browser version, install updates through your organization’s normal process, then repeat the support check and sample-file test.

Separate file handling from device inspection

A hardware inventory may collect device details and also use local files, but those are separate browser capabilities. A browser’s file APIs do not grant access to hardware details, and a hardware information page cannot confirm that an inventory app can open or save a report.

For a closer look at one browser API, see How to check File System Access API support. Keep the distinction clear: an API support result is a compatibility clue, while a successful test in the actual inventory app is evidence that the specific task works on that setup.

Use a copy of a harmless sample file for testing, and remove it when you are finished.