1С-Bitrix Image Resize: Setup, Optimization & Speed

Imagine: an online store catalog on 1С-Bitrix with 10,000 products. Each product has an image of 4000×3000 pixels weighing 8 MB. Without resizing, these files are served in full on every request. The browser scales them via CSS, and you pay for extra gigabytes of traffic and lose visitors due to slow loading. Core Web Vitals suffer. The default Bitrix resizer is far from optimal — quality 85, GD, no pre-generation. We solve this problem comprehensively: choose the library, set parameters, configure caching and pre-generation. As a result, you save from 15,000 to 40,000 rubles per month on traffic for a catalog of 10,000 items.

Why the Default Resize Doesn't Work

Bitrix's built-in resize mechanism uses two APIs: the old CFile::ResizeImageFile() from the main module (via GD) and the new \Bitrix\Main\Web\Image (GD or Imagick). Both cache the result in bitrix/cache/resize_cache/. However, component parameters (e.g., DETAIL_IMAGE_WIDTH in bitrix:catalog.element) are often set to 0 — no resize occurs, the original is served. Even if parameters are set, GD with quality 85 is enabled by default, which is slow and suboptimal for large catalogs.

How to Choose Between GD and Imagick

Imagick is faster and higher quality. You can switch with one line or via the admin panel:

\Bitrix\Main\Config\Option::set('main', 'image_handler', 'imagick');

Check installation: php -r "echo extension_loaded('imagick') ? 'Imagick OK' : 'No Imagick';". On Bitrix VM Imagick is present, on plain PHP-FPM — apt install php-imagick or yum install php-imagick. More about Imagick advantages can be found on Wikipedia.

Setting Quality and Algorithm

\Bitrix\Main\Config\Option::set('main', 'image_resize_quality', '82');
\Bitrix\Main\Config\Option::set('main', 'image_resize_png_quality', '7');

82 for JPEG is a compromise between size and quality. For PNG, 7 out of 9.

Resize Modes and Their Application

In a component template:

$arFile = CFile::ResizeImageGet(
    $arResult['DETAIL_PICTURE'],
    ['width' => 800, 'height' => 600],
    BX_RESIZE_IMAGE_PROPORTIONAL,
    false
);

When Do You Need Pre-generation of Previews?

On first user visit, resize is performed on the fly — causing CPU load and delay. Pre-generation via the OnAfterFileAdd event handler creates previews immediately after file upload:

AddEventHandler('main', 'OnAfterFileAdd', function($arFields) {
    if (in_array($arFields['CONTENT_TYPE'], ['image/jpeg', 'image/png'])) {
        CFile::ResizeImageGet($arFields['ID'], ['width' => 1200, 'height' => 900], BX_RESIZE_IMAGE_PROPORTIONAL);
        CFile::ResizeImageGet($arFields['ID'], ['width' => 400, 'height' => 300], BX_RESIZE_IMAGE_PROPORTIONAL);
    }
});

Limits and Cache Cleanup

Resizing images over 30 MP requires memory_limit = 256M, max_execution_time = 60. For Imagick, also add imagick.skip_secure_multithreaded_extensions = 0.

The preview cache is not automatically cleared when a file is replaced. Safe cleanup by date:

// delete cache older than 30 days
BXClearCache(true, '/');

An alternative is a script using find, but we prefer the programmatic approach.

How We Configure Resize: Process and Case Study

Our typical project — an online store with 50,000 products. Initial state: GD, quality 85, no pre-generation, catalog page load time 8 seconds. We did:

1. Audit current settings — memory_limit, driver, component parameters.
2. Enabled Imagick, set quality to 82.
3. Wrote a pre-generation handler for new files.
4. Updated component templates — set correct sizes and modes.
5. Configured an agent to clear stale cache once a week.
6. Tested — load time dropped to 2.5 seconds, traffic reduced by 65%.

What's Included in the Work

• Audit of current Bitrix and server configuration.
• Selection and activation of the optimal driver (GD/Imagick).
• Setting quality and resize modes for all components.
• Development and implementation of preview pre-generation.
• Optimization of PHP parameters (memory_limit, max_execution_time).
• Configuration of automatic cache cleanup.
• Documentation of all changes made.
• 12-month warranty on the settings.

Timeline and Pricing

Estimated timeline — from 2 to 5 working days depending on catalog size and template complexity. Pricing is calculated individually after an audit. Get a consultation — write to us, we'll evaluate your project.

Our experience of over 10 years and more than 500 projects on Bitrix guarantee that after configuring resize, your store will run faster and Core Web Vitals will be in the green zone. Order an audit and tuning right now. Image optimization recommendations are also described in Google PageSpeed Insights 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.