chrome.fileSystem

Description

Use the chrome.fileSystem API to create, read, navigate, and write to the user's local file system. With this API, Chrome Apps can read and write to a user-selected location. For example, a text editor app can use the API to read and write local documents. All failures are notified via chrome.runtime.lastError.

Permissions

fileSystem

Availability

Foreground only

Types

AcceptOption

Properties

  • description

    string optional

    This is the optional text description for this option. If not present, a description will be automatically generated; typically containing an expanded list of valid extensions (e.g. "text/html" may expand to "*.html, *.htm").

  • extensions

    string[] optional

    Extensions to accept, e.g. "jpg", "gif", "crx".

  • mimeTypes

    string[] optional

    Mime-types to accept, e.g. "image/jpeg" or "audio/*". One of mimeTypes or extensions must contain at least one valid element.

ChooseEntryOptions

Properties

  • accepts

    AcceptOption[] optional

    The optional list of accept options for this file opener. Each option will be presented as a unique group to the end-user.

  • acceptsAllTypes

    boolean optional

    Whether to accept all file types, in addition to the options specified in the accepts argument. The default is true. If the accepts field is unset or contains no valid entries, this will always be reset to true.

  • acceptsMultiple

    boolean optional

    Whether to accept multiple files. This is only supported for openFile and openWritableFile. The callback to chooseEntry will be called with a list of entries if this is set to true. Otherwise it will be called with a single Entry.

  • suggestedName

    string optional

    The suggested file name that will be presented to the user as the default name to read or write. This is optional.

  • type

    ChooseEntryType optional

    Type of the prompt to show. The default is 'openFile'.

ChooseEntryType

Enum

"openFile"
Prompts the user to open an existing file and returns a FileEntry on success. From Chrome 31 onwards, the FileEntry will be writable if the application has the 'write' permission under 'fileSystem'; otherwise, the FileEntry will be read-only.

"openWritableFile"
Prompts the user to open an existing file and returns a writable FileEntry on success. Calls using this type will fail with a runtime error if the application doesn't have the 'write' permission under 'fileSystem'.

"saveFile"
Prompts the user to open an existing file or a new file and returns a writable FileEntry on success. Calls using this type will fail with a runtime error if the application doesn't have the 'write' permission under 'fileSystem'.

"openDirectory"
Prompts the user to open a directory and returns a DirectoryEntry on success. Calls using this type will fail with a runtime error if the application doesn't have the 'directory' permission under 'fileSystem'. If the application has the 'write' permission under 'fileSystem', the returned DirectoryEntry will be writable; otherwise it will be read-only. New in Chrome 31.

RequestFileSystemOptions

Chrome 44+

Properties

  • volumeId

    string

    The ID of the requested volume.

  • writable

    boolean optional

    Whether the requested file system should be writable. The default is read-only.

Volume

Chrome 44+

Properties

  • volumeId

    string

  • writable

    boolean

VolumeListChangedEvent

Chrome 44+

Properties

Methods

chooseEntry()

chrome.fileSystem.chooseEntry(
  options?: ChooseEntryOptions,
  callback: function,
)

Ask the user to choose a file or directory.

Parameters

  • options
  • callback

    function

    The callback parameter looks like:

    (entry?: Entry, fileEntries?: FileEntry[]) => void

    • entry

      Entry optional

    • fileEntries

      FileEntry[] optional

getDisplayPath()

Promise
chrome.fileSystem.getDisplayPath(
  entry: Entry,
  callback?: function,
)

Get the display path of an Entry object. The display path is based on the full path of the file or directory on the local file system, but may be made more readable for display purposes.

Parameters

  • entry

    Entry

  • callback

    function optional

    The callback parameter looks like:

    (displayPath: string) => void

    • displayPath

      string

Returns

  • Promise<string>

    Chrome 117+

    Promises are only supported for Manifest V3 and later, other platforms need to use callbacks.

getVolumeList()

Promise Chrome 44+
chrome.fileSystem.getVolumeList(
  callback?: function,
)

Returns a list of volumes available for requestFileSystem(). The "fileSystem": {"requestFileSystem"} manifest permission is required. Available to kiosk apps running in the kiosk session only. In case of an error, volumes will be undefined, and chrome.runtime.lastError will be set.

Parameters

  • callback

    function optional

    The callback parameter looks like:

    (volumes?: Volume[]) => void

Returns

  • Promise<Volume[] | undefined>

    Chrome 117+

    Promises are only supported for Manifest V3 and later, other platforms need to use callbacks.

getWritableEntry()

chrome.fileSystem.getWritableEntry(
  entry: Entry,
  callback: function,
)

Get a writable Entry from another Entry. This call will fail with a runtime error if the application does not have the 'write' permission under 'fileSystem'. If entry is a DirectoryEntry, this call will fail if the application does not have the 'directory' permission under 'fileSystem'.

Parameters

  • entry

    Entry

  • callback

    function

    The callback parameter looks like:

    (entry: Entry) => void

    • entry

      Entry

isRestorable()

Promise
chrome.fileSystem.isRestorable(
  id: string,
  callback?: function,
)

Returns whether the app has permission to restore the entry with the given id.

Parameters

  • id

    string

  • callback

    function optional

    The callback parameter looks like:

    (isRestorable: boolean) => void

    • isRestorable

      boolean

Returns

  • Promise<boolean>

    Chrome 117+

    Promises are only supported for Manifest V3 and later, other platforms need to use callbacks.

isWritableEntry()

Promise
chrome.fileSystem.isWritableEntry(
  entry: Entry,
  callback?: function,
)

Gets whether this Entry is writable or not.

Parameters

  • entry

    Entry

  • callback

    function optional

    The callback parameter looks like:

    (isWritable: boolean) => void

    • isWritable

      boolean

Returns

  • Promise<boolean>

    Chrome 117+

    Promises are only supported for Manifest V3 and later, other platforms need to use callbacks.

requestFileSystem()

Promise Chrome 44+
chrome.fileSystem.requestFileSystem(
  options: RequestFileSystemOptions,
  callback?: function,
)

Requests access to a file system for a volume represented by options.volumeId. If options.writable is set to true, then the file system will be writable. Otherwise, it will be read-only. The writable option requires the "fileSystem": {"write"} permission in the manifest. Available to kiosk apps running in kiosk session only. For manual-launch kiosk mode, a confirmation dialog will be shown on top of the active app window. In case of an error, fileSystem will be undefined, and chrome.runtime.lastError will be set.

Parameters

  • callback

    function optional

    The callback parameter looks like:

    (fileSystem?: FileSystem) => void

    • fileSystem

      FileSystem optional

Returns

  • Promise<FileSystem | undefined>

    Chrome 117+

    Promises are only supported for Manifest V3 and later, other platforms need to use callbacks.

restoreEntry()

chrome.fileSystem.restoreEntry(
  id: string,
  callback: function,
)

Returns the file entry with the given id if it can be restored. This call will fail with a runtime error otherwise.

Parameters

  • id

    string

  • callback

    function

    The callback parameter looks like:

    (entry: Entry) => void

    • entry

      Entry

retainEntry()

chrome.fileSystem.retainEntry(
  entry: Entry,
)

Returns an id that can be passed to restoreEntry to regain access to a given file entry. Only the 500 most recently used entries are retained, where calls to retainEntry and restoreEntry count as use. If the app has the 'retainEntries' permission under 'fileSystem', entries are retained indefinitely. Otherwise, entries are retained only while the app is running and across restarts.

Parameters

  • entry

    Entry

Returns

  • string

Events

onVolumeListChanged

Chrome 44+
chrome.fileSystem.onVolumeListChanged.addListener(
  callback: function,
)

Called when a list of available volumes is changed.

Parameters