Site ↗
Documentation sections
UI interface · 0.8.1

Content / Images: upload and variants

Configure Image/Gallery, file limits, cropping, sizes and website URLs.

On this page

Adding a media field

In a persistent entity, Add field → Image for one image or Gallery for several. Set name, requirement and Image settings. Finish and Generate.

The generator configures processing rules; users upload actual files in generated-admin record forms.

Upload limits

Setting Purpose
Allowed formats Source JPEG, PNG, WebP
Maximum file size (MiB) File-size limit
Maximum megapixels Pixel-count limit
Maximum images Gallery only: maximum including pending uploads

Choose limits for project materials. Screenshots need readable text and sufficient width; photo-style strict cropping may remove UI content.

Profile, crop and sizes

Start with Size profile: photo, avatar, cover, custom. Crop offers Original proportions, Square (1:1), Widescreen (16:9), Custom ratio. Set Ratio width/height for custom ratios.

Output sizes defines variant names/widths. Add size or Remove size; at most four variants. Images smaller than a selected size are not artificially upscaled.

Example variant Width Use
sm 320 Compact card
md 960 Content column
lg 1600 Large screenshot

These are example variants; choose your own names/widths. sm/md/lg are optional conventions.

Output format offers Automatic, JPEG, PNG. Automatic preserves transparency in PNG; explicit JPEG rejects transparent images. JPEG quality affects JPEG only. Settings affect new processing; saved variants are not automatically regenerated.

Storage

Choose Local files or Private S3-compatible storage project-wide in Project settings. Bucket/secrets belong to the application environment, not field settings. Backend serves images in both modes.

Virtual and external images

Virtual can select source/related persistent image/gallery fields. Projections cannot upload/delete media. Admin viewing requires source image-owner permissions; virtual access alone is insufficient.

External API returns direct URLs keyed by configured sizes:

{
  "image": {
    "assetId": "…",
    "alt": "Экран настройки полей",
    "size": {
      "sm": "https://example.com/…",
      "md": "https://example.com/…"
    }
  }
}

Choose a size on the website and place its URL in the image. No metadata request is needed. Anyone knowing the URL can currently open it. Publication rules restrict record responses but do not instantly revoke issued URLs. Account for small possible cache delays when changing visibility.

See CLI image/gallery parameters, storage configuration.