Simple file system API for React Native on iOS & Android & Windows.
Switch branches/tags
Nothing to show
Clone or download
Latest commit 8b7c31d Nov 20, 2017

This is a forked repository of benwixen's react-native-filesystem with purpose to support React Native Windows.

react-native-filesystem-v1 npm version

Simple file system access on iOS & Android & Windows.

All interaction is promise-based, and all content is written and read as UTF-8.


npm install react-native-filesystem-v1 --save
react-native link react-native-filesystem-v1

This project is based on the 9-project-layout.


For a full list of available methods, see the API Reference.

Write to files

import FileSystem from 'react-native-filesystem-v1';

async function writeToFile() {
  const isAppend = true; // If this variable is set to true, content will be appended to the file.
  const fileContents = 'This is a my content.';
  await FileSystem.writeToFile('my-directory/my-file.txt', fileContents, isAppend);
  console.log('file is written');

Sub-directories are created automatically.

Read from files

async function readFile() {
  const fileContents = await FileSystem.readFile('my-directory/my-file.txt');
  console.log(`read from file: ${fileContents}`);

Delete files or folders

async function deleteFile() {
  await FileSystem.delete('my-directory/my-file.txt');
  console.log('file is deleted');

Check if files or directories exist

async function checkIfFileExists() {
  const fileExists = await FileSystem.fileExists('my-directory/my-file.txt');
  const directoryExists = await FileSystem.directoryExists('my-directory/my-file.txt');
  console.log(`file exists: ${fileExists}`);
  console.log(`directory exists: ${directoryExists}`);

Selecting a storage class

All commands also take an optional last argument specifying a storage class. These classes roughly correspond to the four points of the iOS Data Storage Guidelines, and have similar behaviour on Android. Example usage:

FileSystem.writeToFile('my-file.txt', 'My content', false,;

Files need to be read from the same storage class they're saved to, and two files can have the same name if they're located in different storages. The options are:

Storage class Description
storage.backedUp These files are automatically backed up on supported devices
storage.important Excluded from backup, but still kept around in low-storage situations
storage.auxiliary Files that the app can function without. Can be deleted by the system in low-storage situations.
storage.temporary For temporary files and caches. Can be deleted by the system any time.

For full details, see the API Reference.


Why yet another file system library?
I simply couldn't find one that satisfied my basic needs for simplicity.

Why not use the built-in AsyncStorage?
AsyncStorage is fine, but some times you want more control as to where the content is stored. This library lets you put it in backed-up folders, or play nice by marking content that can be deleted when the phone runs low on space.