Volumes on the Hobby plan are capped at 5 GB, so you cannot store 60 GB in a volume on Hobby. You would need the Pro plan ($20/month), which supports volumes up to 50 GB self-serve (larger by request). Volume storage is billed at $0.15/GB/month, so 60 GB would add roughly $9/month on top of the plan fee. If your use case fits object storage instead of block storage, Buckets are available on Hobby at $0.015/GB/month with a 1 TB cap.

Ok

If I take the hobby of 5 dollars subscription per month

beside that, I make another subscription in cloudfare for additional space nothing else, How can we manage the process of uploading files on our website (the hobby) but using the space of cloudfare at the same time

yes, you can do that, but your app has to upload directly to Cloudflare storage, not to the Railway volume.

usually that means using Cloudflare R2. you store only the file URL/key in your database, and the actual file goes to R2 using S3-compatible credentials.

so Railway Hobby can run the website/app, while R2 handles the 60GB files. just dont use Railway local filesystem for uploads, because deploys/restarts and the 5GB Hobby volume limit will keep biting you.

Yes, that setup works, but the important part is that uploads should not land on the Railway filesystem or a Railway volume first.

A good architecture is:

1. Keep the app/web server on Railway Hobby.
2. Create object storage separately: Cloudflare R2, or Railway Buckets if you want to keep it inside Railway.
3. Store only metadata in your database: object key, filename, MIME type, size, owner/user id, and public/private URL state.
4. For uploads, have your backend create a short-lived presigned PUT URL, then let the browser upload directly to R2/Bucket storage.
5. For downloads, either serve public files through a public bucket/custom domain, or have the backend create a short-lived presigned GET URL for private files.

That means the 60 GB of files never consumes your 5 GB Railway volume. Railway just runs your app and database logic.

For Cloudflare R2, use its S3-compatible API and presigned URLs. Do not put the R2 secret/access key in frontend code; keep those as Railway service variables and only let your backend mint temporary upload/download URLs. Cloudflare notes that presigned URLs can allow PUT/GET/HEAD/DELETE on a single object for a limited time: https://developers.cloudflare.com/r2/api/s3/presigned-urls/

If you use Railway Buckets instead, the current docs say Hobby supports up to 1 TB combined bucket storage and storage is billed at $0.015/GB-month: https://docs.railway.com/storage-buckets/billing

One billing detail: if your Railway service receives the file first and then uploads it to storage, that traffic can count as Railway service egress. Direct browser-to-storage upload is usually the cleaner flow.