Home / Product / Files and images

Store product content

Keep every file beside the customer, record, or workflow it belongs to.

Add documents, images, video, and other assets to application records so access, ownership, and product behavior stay connected.

See what it changes Technical guide ↗

Files and images in a product

A record needs contentProfile photo, contract, product image, attachment

Store the asset with contextKeep metadata and ownership beside it

Use it across the productDownload, transform, publish, or act

Content keeps its product context

01Avoid a separate file identity systemAttach content to the record people already understand.

02Carry access into deliveryCheck the parent record before serving its file.

03Create useful image variantsResize, crop, rotate, blur, or adjust presentation when needed.

Why it matters

A file is rarely just a URL. It belongs to someone and means something.

A contract belongs to a customer. A product photo belongs to an item. An attachment belongs to a support request. When files live in a disconnected bucket, every application feature must rebuild that ownership and access context.

Daptin asset fields make files part of ordinary records. The backend keeps file metadata with the subject, checks access through that record, and can store the bytes inline or in connected storage.

The same file can then participate in APIs, administration, image transformations, actions, sites, and synchronization without becoming an ungoverned side channel.

Give content a clear owner

Keep the file attached to the customer, project, article, or other record that gives it meaning.

Protect downloads through the product

Use record access rather than relying on hard-to-audit public object URLs.

Prepare content for the experience

Create image variants and deliver byte ranges where the client needs them.

How it fits

Part of one connected backend.

Files and images does more when it can reuse the records, people, access rules, and workflows already in your application.

Step 1Attach

Add an asset field to the relevant record type.

Step 2Upload

Send the file directly or through the supported large-file path.

Step 3Store

Keep it inline or use a connected cloud store.

Step 4Serve

Deliver it through the record's access and cache path.

What it enables

Use it in products people recognize.

Start from the experience you want to create; the backend capability supports the work behind it.

Customer documents

Store agreements, evidence, or reports beside the account or case.

Product media

Attach reusable images and variants to catalogue items.

Collaborative attachments

Keep project files visible to the same members as the record.

Connected by design

Build the next part without starting over.

These capabilities share the same application context, so each one makes files and images more useful.

Know the boundary

What Daptin leaves in your hands.

Files remain subject to storage capacity, provider limits, backup design, malware handling, retention, and privacy obligations. Review which asset types belong inline and which should use external storage.

Understand the operating responsibility →

Build from one foundation

Make files and images part of the product—not another disconnected service.

Run Daptin locally, explore the live administration surface, and follow one complete application path.

Get Daptin Explore all capabilities