Give content a clear owner
Keep the file attached to the customer, project, article, or other record that gives it meaning.
Home / Product / Files and images
Store product contentAdd documents, images, video, and other assets to application records so access, ownership, and product behavior stay connected.
A contract belongs to a customer. A product photo belongs to an item. An attachment belongs to a support request. Represent stored bytes as Daptin file records so APIs, actions, sites, and transformations reuse their 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.
Keep the file attached to the customer, project, article, or other record that gives it meaning.
Attach files and images to records with the same ownership and permission context.
Create image variants and deliver byte ranges where the client needs them.
A product photo, case attachment, document, audio file, or video keeps its name, size, location, owner, and chosen file service together.
Files and images does more when it can reuse the records, people, access rules, and workflows already in your application.
Add an asset field to the relevant record type.
Send the file directly or through the supported large-file path.
Keep it inline or use a connected cloud store.
Deliver it through the record's access and cache path.
Start from the experience you want to create; the backend capability supports the work behind it.
Store agreements, evidence, or reports beside the account or case.
Attach reusable images and variants to catalogue items.
Keep project files visible to the same members as the record.
These capabilities share the same application context, so each one makes files and images more useful.
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.
Run Daptin locally, explore the live administration surface, and follow one complete application path.