Short answer: keep private user-uploaded images and derived thumbnails in object storage, keep ownership and deletion state in the database, and deliver each object to an authenticated browser with a short-lived signed URL.
Where the byte multiplier enters the bill
For a European SaaS application, the recurring bill is made of stored bytes, operations, and delivery, while a database-BLOB design also makes binary growth part of database backup and operational planning. The dominant storage term is usually the multiplication of one original into retained variants: an original plus every thumbnail is more bytes kept until deletion. The useful change is therefore architectural, not a vendor discount: generate only the sizes the product serves, put those files under one deterministic prefix, and delete the entire set at the explicit deadline.
This is also a trust-boundary decision.…