Scope: the Digital Asset Management capabilities of the Pimcore platform, Platform Version 2026.3. Each line says which edition a feature needs: Core = every edition including Community; Enterprise = Enterprise and Enterprise PaaS only S2. PIM, MDM and CMS features are mentioned only where they shape the DAM: assets, data objects and documents share one repository S95.
Ingestion & storage
- Any file type can be stored as an asset. Previews are generated for images (ImageMagick formats such as JPG, PNG, EPS, PSD, TIFF, SVG), video (FFmpeg formats such as AVI, MP4, MKV, MOV) and Office/PDF documents (via LibreOffice or Gotenberg) S26 S29. The product page claims previews for "200+" formats, with 3D/AR "depending on setup" S1. Core
- Upload paths: Studio UI (drag and drop; at most 5 parallel uploads by default, configurable) S40; ZIP upload that unpacks into assets, via the Studio API S60; WebDAV mount of the whole asset tree at
/asset/webdav, using Pimcore user credentials and permissions S31; PHP API for importers S32; Datahub GraphQL mutations S65; Portal upload dialogs and upload folders (Enterprise) S44. Hot folders and a dedicated desktop uploader: Not public (none documented; Direct Edit only edits existing assets). - File size limits: no product limit is documented. They depend on server settings (the PHP
upload_max_filesize/post_max_sizeminimum is 100 MB, "depending on your data") S36. - Storage: Flysystem storage adapters for originals, generated files, thumbnails, versions and the recycle bin. Local disk by default, with S3 and other adapters; clusters need shared storage S33. The product page claims "unlimited cloud storage" S1 Unverified (marketing; actual limits depend on hosting).
- Versioning: every save creates a version, with no cap unless retention limits are set. Versions can be compared, restored or published.
skip_initial_versionavoids storing a binary copy of assets that are never modified S34. Core - Recycle bin for deleted elements S37 S60. Core
- CDN: frontend URL prefixes for originals and thumbnails (e.g. CloudFront) S33. Since 2026.2, core events invalidate CDN caches per asset or thumbnail, with a built-in Fastly implementation S10. PaaS includes Fastly S15.
Metadata & taxonomy
- Custom metadata (Core): editable, localizable fields per asset, plus "predefined metadata" templates managed in Studio S26 S32 S60.
- Embedded metadata: EXIF, IPTC and XMP are read and displayed read-only. Pimcore cannot edit or write back embedded metadata S26.
- Asset Metadata Class Definitions (Enterprise): metadata schemas defined like data object classes, several definitions per asset, extra data types (multi-select, many-to-many relations to objects/assets, calculated values…) and grid filtering on relation fields S42 S6.
- Tags: centrally defined hierarchical tags for assets, documents and objects, with separate permissions for configuring, assigning and searching S35. Properties (inheritable down the tree) and developer-facing custom settings also exist S32.
- Links to product data: assets are referenced from data object relation and image fields, and those references are tracked as dependencies and usages S95 S60. Core
- Bulk edit: the Studio API patches many assets at once, or every asset in a folder matching filters S60. Backend Power Tools adds bulk editing and batch operations (Enterprise) S3.
- Translation of metadata: asset metadata can be sent to DeepL or translations.com through Translation Provider Interfaces (Enterprise) S80.
- Required fields and controlled vocabularies: available through data types in metadata class definitions (Enterprise) S42. Validation rules for core custom metadata: Unknown.
Search & discovery
- Generic Data Index (Core) indexes assets, objects and documents in OpenSearch (≥ 2.7, recommended) or Elasticsearch (≥ 8). Studio needs it S36 S3.
- Full-text search across elements; extracted PDF/Office text is indexed S60 S29.
- Pimcore Query Language (PQL): field comparisons, wildcard
LIKE,NULL/EMPTY, AND/OR, relation filters (e.g.main_image:Asset.type) and raw query-string queries S43. - Saved searches that users can share, update and add to the menu (2026.2) S10. Tag filters in search S35.
- Semantic and image search (Enterprise, experimental, off by default): embeddings from an inference service you provide allow natural-language image search ("yellow van") without tags S41 S11.
- Facets: portals and Datahub Simple REST offer filters and aggregations (Enterprise) S44 S70.
AI capabilities
- Pimcore Copilot (Enterprise): actions run from Studio (Alt + X), as background automations or as chat-like interactions S51. Shipped steps include Hugging Face models (image classification, zero-shot classification, image-to-text, text-to-image, image upscaling, translation), OpenAI-compatible text generation, writing results to asset metadata, and automatic linking of images to data objects from metadata S52.
- Embeddings (Enterprise, experimental): semantic search, image duplicate and near-duplicate detection. Vectors are stored in the index; no model is bundled S41.
- Pimcore Agent chat agents in Studio: search and read assets, propose metadata changes for human approval, upload and update assets. The default setup uses GitHub Copilot with Claude Haiku 4.5; other inference providers can be configured S54 S55. Its edition and general availability are Unknown (installed as
dev-main; private repository S90). - OCR, speech-to-text transcription, face recognition: Not public (no shipped action documented; can be built as custom Copilot steps S51).
- AI governance: AI features are opt-in modules, permission-gated, and use providers the customer configures S41 S51 S54.
Organization
- Folder tree with permissions per folder; an asset belongs to exactly one folder path S26 S37.
- Collections in portals: personal or shared (read-only or edit), downloadable as ZIP, also manageable from the Studio backend (Enterprise) S45.
- Portals: several Asset and Product Experience Portals per installation, configured without code, multi-language and multi-tenant (Enterprise, Portal Engine) S44. Portals have configurable dashboard and content pages; a dedicated brand-guidelines module is Not public S44.
- Perspectives (customisable Studio layouts per user group) S60.
Workflow & collaboration
- Workflow engine (Core) based on Symfony Workflow: several workflows per element, places, transitions with guards, required notes and per-place permissions. Applies to assets too S53. Workflow Designer is a visual editor (Enterprise) S2.
- Notes & Events comments/log on assets S39; notifications, with per-user channel choice (in-app, email) since 2026.3 S11; edit locks on elements S60.
- Direct Edit (Enterprise): an "Edit Locally" action opens the asset in the editor's desktop application through an Electron client (Windows, macOS). Changes upload back as a new version, with conflict resolution S49 S50.
- Scheduling: scheduled actions per element (e.g. publish or delete at a date) S60.
- Visual proofing and annotation on images/video: Not public (not documented).
Rights & governance
- Permissions: users and roles. System permissions plus workspaces: per-folder element permissions (list, view, save, publish, delete, rename, settings, versions, properties) inherited by children; user settings override role settings S37. Datahub endpoints add their own workspaces S63.
- Public-by-default delivery: assets are served directly by the web server unless protected folders are set up S30.
- Rights metadata: copyright and licence data are kept as metadata fields S1. Dedicated usage-rights, expiry or embargo objects: Not public. Expiry can be modelled with workflows and scheduled actions S53 S60 Unverified (inference; no packaged rights module documented).
- Watermarking: listed on the product page S1; the documented core transformation list (resize, scale, contain, crop, cover, frame, rotate, background colour, rounded corners) has no watermark step S27 Unverified (how watermarking is done is not documented).
- Audit trail: versions, Notes & Events, an application logger and a GDPR data extractor S34 S39 S60.
- Retention: version count and age limits; recycle bin S34. Legal hold and records retention: Not public.
Distribution & delivery
- Thumbnail pipeline (Core): named or dynamic image transformations (resize, scale, contain, cover with focal point, crop, frame, rotate, background colour, rounded corners), with auto format that serves WebP/AVIF variants,
srcsetand<picture>output, and deferred on-demand rendering S27. - Direct file URLs: originals and thumbnails are served by path, optionally behind a CDN prefix S33.
- Portals (Enterprise): download in configured formats, download cart, ZIP packaging in the background, public share links for collections, guest access S45 S46 S47.
- APIs for channels: Datahub GraphQL (Core), Datahub Simple REST, File Export and Webhooks (Enterprise) S2 S61.
- Print: Web-to-Print documents and PDF generation (Enterprise) S3. Partner print/publishing connectors are listed on the Integrations page.
- Brand templating (editable layouts for marketers): Not public for DAM. Web-to-Print documents cover catalogue-style output S3.
Video & rich media
- Video transcoding with FFmpeg into web formats (MP4, WebM…), frame-rate, cut, mute and colour-mixer transformations, still frames at a chosen second S28.
- Adaptive streaming: MPEG-DASH (
.mpd) output from bitrate-based thumbnail configs S28. - Documents: page thumbnails for PDF and Office files, page count, text extraction for search, and a scan of PDFs for embedded JavaScript S29.
- Subtitles/captions, audio waveforms and 3D viewers: Not public (product page says 3D/AR previews are "depending on setup") S1.
Analytics & reporting
- Portal statistics (Enterprise): logins per week, most downloaded assets, downloads over time by context and by thumbnail, and asset storage by type S48.
- Statistics Explorer and Studio Dashboards (Enterprise): custom reports (list and statistics modes, no SQL needed) and KPI widgets, including data quality and workflow widgets S6 S10 S3.
- Element usage: dependencies and usages of each asset S60.
- Exports of grids to CSV/XLSX S60.
Administration
- Admin UI: Pimcore Studio (React), the only supported UI since 2026.1. The ExtJS Admin UI Classic was removed S9.
- Users & roles in Studio. Two-factor authentication can be enforced S37 S38. OIDC SSO with claim-to-role mapping (Enterprise) S78. SCIM: Unknown.
- Multi-tenant / multi-brand: one installation can run several sites and several portals S95 S44. Separate tenants in one install: Not public.
- Environments: configuration (Datahub, thumbnails, workflows) is stored as YAML and deployed through version control S68. PaaS offers preview/staging environments with automatic stop and start S14 S15.
- Upgrades: Platform Version metapackage, one major release per year and minor releases about quarterly. LTS (3 years for 2025.4) only in Enterprise S7 S89.
- Product registration key required per instance S88.