Prompt
What’s the right storage option if I need old application files archived cheaply but still searchable sometimes?
Latest observation
Oct 12, 2026
OpenAI APIWeb search: off
For cheap archival storage that you can still search occasionally, the best fit is usually cloud archive storage with a small “hot” metadata index.
Best storage class
Use a cold/archive tier such as:
- Amazon S3 Glacier / Glacier Deep Archive
- Azure Blob Archive
- Google Cloud Storage Archive / Coldline
These are designed for:
- very low cost per GB
- rare access
- long-term retention
How to make it searchable
Archive storage itself is not meant for fast searching. A common pattern is:
- Store the actual files in archive storage
- Keep metadata/index info in a normal database or search engine
- e.g. PostgreSQL, DynamoDB, Elasticsearch/OpenSearch, or even a simple catalog table
- Search the metadata first
- Restore/download only the matching archived files when needed
If you need occasional full-text search
If “searchable” means searching inside the files themselves:
- keep indexed copies or extracted text in a searchable system
- or maintain a hot tier for recent/important files
- while the originals live in archive storage
Good rule of thumb
- Rarely accessed, cheap retention: archive storage
- Need to search often: keep metadata/index in hot storage
- Need to search contents sometimes: archive originals + searchable text index
Practical recommendation
A strong default setup is:
- Archive files: S3 Glacier Deep Archive (or equivalent)
- Search/catalog: PostgreSQL or OpenSearch with file name, date, tags, and extracted text
- Workflow: search index → restore archived file if needed
If you want, I can suggest the best option by cloud provider or by budget/access frequency.