Applications often need to handle file uploads and storage, from user avatars and documents to images and other media. Neon does not yet provide a native file storage solution. Instead, we recommend combining Neon with a specialized storage service.
The typical pattern looks like this:
- Upload files from your application (client or backend) to an object storage provider or file management service.
- Store references—such as the file URL, unique key, or identifier—and related metadata like user ID, upload timestamp, file type, size, and permissions in your Neon Postgres database.
This pattern separates file storage from relational data management, with purpose-built services like S3 or R2 handling file storage and Neon managing your data.
Options for external storage
You can integrate Neon with a variety of storage solutions:
- S3-compatible object storage: Services like AWS S3, Cloudflare R2, and Backblaze B2 offer file storage via the widely-adopted S3 API.
- File and media management SaaS platforms: Services like ImageKit, Cloudinary, Uploadcare or Filestack provide higher-level abstractions, often including additional features like image optimization, transformations, and SDKs, while managing the underlying storage infrastructure for you.
AWS S3
Upload files to AWS S3 and store metadata in Neon
Azure Blob Storage
Upload files to Azure Blob Storage and store metadata in Neon
Backblaze B2
Upload files to Backblaze B2 and store metadata in Neon
Cloudflare R2
Upload files to Cloudflare R2 and store metadata in Neon
Cloudinary
Upload files to Cloudinary and store metadata in Neon
ImageKit
Upload files to ImageKit and store metadata in Neon
Uploadcare
Upload files to Uploadcare and store metadata in Neon
Need help?
Join our Discord Server to ask questions or see what others are doing with Neon. Users on paid plans can open a support ticket from the console. For more details, see Getting Support.