GoogleChromeLabs/browser-fs-access

Health v2 · maintenance only

Adoption not part of the score

1581 stars · 98 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

A JavaScript ponyfill library that provides the File System Access API on supporting browsers with a transparent fallback to legacy <input type="file"> and <a download> methods. It lets web apps open, save, and read files and directories through a single unified API regardless of browser support.

Use cases

• open files in the browser with a unified api
• save files to disk from a web app
• read all files in a directory from the browser
• use file system access api with fallback for older browsers
• feature-detect file system access api support
• open multiple files with mime type filters in javascript
• stream a response or promise blob to a file download

When to choose

• You need file open/save/directory access in a web app that must work across browsers, including ones without the File System Access API
• You want progressive enhancement: native File System Access API where available, legacy input/download fallbacks elsewhere
• You need to open files or directories with MIME/extension filtering through a small, tree-shakeable module

When to avoid

• You are building a Node.js or server-side application rather than a browser app
• You only target browsers that fully support the File System Access API and don't need a fallback
• You need low-level filesystem operations like writing to arbitrary paths without user interaction

Facets

library · maturity active

file-system file-upload sdk web-development frontend files cross-platform browser file-system-access-api ponyfill progressive-enhancement file-open file-save directory-open browser-api fallback javascript nodejs

Member repositories

For agents

markdown · JSON · MCP: product_card(name="GoogleChromeLabs/browser-fs-access")