DAM Setup for 1C-Bitrix: Digital Asset Management

DAM (Digital Asset Management) Setup for 1C-Bitrix

We configure DAM on top of the 1C-Bitrix media library. The standard fileman module is a simple file tree without metadata, full-text search, or file-level permissions. Result: 30–40% duplicates, finding a file takes 15 minutes, no version control. Our engineers with 5+ years of experience solve the problem: we add hierarchical tags, UF fields, link files to products without duplication, and set up versioning. A typical project pays for itself in 3–4 months by cutting duplicates, leading to significant savings on storage.

Why the Standard Media Library Falls Short

The b_file table is the central registry of all files. It contains basic fields: ID, MODULE_ID, HEIGHT, WIDTH, FILE_SIZE, CONTENT_TYPE, SUBDIR, FILE_NAME, ORIGINAL_NAME, DESCRIPTION, HANDLER_ID. On top of it, the media library adds a folder structure (b_medialib_collection) and file-to-collection links (b_medialib_item). Each item has only a KEYWORD field (comma-separated tags) and DESCRIPTION. This is insufficient for a full DAM. Missing: hierarchical tags, versioning, per-file permissions, and content-based search. We address these.

How to Integrate DAM with the Product Catalog?

The main challenge is linking media files to products so that one image can be used in multiple items without file duplication. In Bitrix, this is done via an infoblock property of type "Link to media library elements" (E:MEDIALIB). When the file in the media library changes, all linked products automatically get the updated version. We also set up automatic linking via agents: when an image is uploaded to the media library, a product is created or its visuals are updated. This reduces manual linking time by 95%.

What UF Fields Are Needed for DAM?

User fields (UF) are added via the interface: Settings → Users → User fields → Object type MEDIALIB_ITEM. Typical set:

• UF_COPYRIGHT – copyright holder (string)
• UF_LICENSE – license type (list)
• UF_EXPIRY_DATE – rights expiry date (date)
• UF_USAGE_RIGHTS – usage scope (multiple list)
• UF_PHOTOGRAPHER – author (string)

After adding, fields are accessible via CMedialibItem::GetList() API. For full-text search on UF fields, we activate the search module and write an indexing agent.

Comparison: Standard Media Library vs DAM (Our Setup)

Media Library Search: Custom Query

Standard search works only on NAME and KEYWORD. For UF field search you need a custom query:

$items = CMedialibItem::GetList([
    'order'  => ['ID' => 'DESC'],
    'filter' => [
        'KEYWORD' => 'product-photo',
        'UF_LICENSE' => 'royalty-free',
    ],
    'arSelectFields' => ['ID', 'NAME', 'FILE_ID', 'UF_COPYRIGHT'],
]);

For full-text search over all metadata, activate the search module—in CSearch::Index() we index UF fields. We set up an agent with periodic indexing every 15 minutes.

Upload via API: Example

Programmatic file upload to media library with metadata:

CModule::IncludeModule('fileman');

$fileId = CFile::SaveFile([
    'name'       => 'product-main.jpg',
    'type'       => 'image/jpeg',
    'tmp_name'   => '/tmp/upload.jpg',
    'MODULE_ID'  => 'fileman',
], 'medialib');

$itemId = CMedialibItem::Add([
    'COLLECTION_ID' => $collectionId,
    'FILE_ID'       => $fileId,
    'NAME'          => 'Фото товара',
    'KEYWORD'       => 'каталог, сезон',
    'FIELDS'        => [
        'UF_COPYRIGHT' => 'Acme Studio',
        'UF_LICENSE'   => 'royalty-free',
    ],
]);

Work Process: From Audit to Deployment

1. Audit – analyze current media library structure, file storage, duplicate count, metadata. (1–2 days)
2. Design – design collection hierarchy, define UF fields, access rights, catalog linking scheme. (1 day)
3. Implementation – create UF fields, configure search, versioning, agents, write custom display components. (3–5 days)
4. Testing – verify upload, search, product linking, access rights, performance. (1–2 days)
5. Deployment – release to production, train editors. You receive full documentation and source code.

Timeline – from 1 to 3 weeks depending on scope. We evaluate your project for free in 1 day. Contact us for a consultation.

What’s Included in the Setup

• Audit of current media library structure and file storage
• Creation of collection hierarchy tailored to the project
• Addition of UF fields for extended metadata
• Configuration of media library–catalog linking
• Implementation of extended metadata search
• Configuration of collection access rights by user groups
• Versioning via events (optional)
• Integration with REST API for external access

We guarantee the functionality specified in the technical requirements. Order the setup—get a DAM that reduces file search time by 3x and lowers duplicates to <5%. More details on media library capabilities in the official documentation.

What Professional 1C-Bitrix Installation Includes

We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.

How to Choose Hosting and Edition for 1C-Bitrix Installation?

BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.

VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.

Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.

What Server Settings Are Critical for 1C-Bitrix?

Web Server and PHP

nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.

Database and Caching

MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:

'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]

sudo apt install redis-server
sudo systemctl enable redis

SSL, Email, and Cron

SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.

Security and Administration

File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.

How Long Does 1C-Bitrix Installation and Configuration Take?

Post-Installation Checklist

1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
3. Security Scanner — check for typical vulnerabilities.
4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
5. Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.

Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.

Deliverables

• Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
• Installed and activated license of the required edition.
• SSL certificate, email settings, cron and backups.
• Documentation: all configuration parameters, access credentials, cron tasks.
• Content manager training: how to log into admin panel, add products, upload images.
• Post-installation support for 30 days — consultations on settings.

Why Trust Professionals with Installation?

Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.