---
title: "File Storage Overview"
slug: "file-storage-overview"
updated: 2024-09-17T10:42:51Z
published: 2024-09-17T10:42:51Z
canonical: "help.hyperscience.ai/file-storage-overview"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.hyperscience.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# File Storage Overview

## File storage

As described in [Infrastructure Requirements (Production)](/deployment/docs/infrastructure-requirements#h_01H93A0FQN3HEZP26MTJ67N2GP), a file storage location will need to be provided. The instructions for configuring the different options can be found in the articles below:

- [S3 Cloud Storage](/deployment/docs/s3-cloud-storage)
- [Azure Blob Storage](/deployment/docs/azure-blob-storage)
- [Google Cloud Storage](/deployment/docs/google-cloud-storage)
- [Network-attached Storage or Local Storage](/deployment/docs/network-attached-storage-or-local-storage)

### *HS_PATH/media* verification

By default in v35.0.24+ and v37 and later, *run.sh init* verifies the presence and ownership of *HS_PATH/media*. If *HS_PATH/media* does not exist or is not owned by *uid 1000* and *gid 1000*, the file store will not be initialized, and the application initialization will fail.

If you need to bypass this verification (e.g., for debugging purposes), you can add *HS_RUN_ON_BROKEN_MEDIA_DIR=true* to your ".env" file. Do not add this variable unless instructed to do so by Hyperscience.