Configuring WebP Image Conversion in 1C-Bitrix

Our company is engaged in the development, support and maintenance of Bitrix and Bitrix24 solutions of any complexity. From simple one-page sites to complex online stores, CRM systems with 1C and telephony integration. The experience of developers is confirmed by certificates from the vendor.
Showing 1 of 1All 1626 services
Configuring WebP Image Conversion in 1C-Bitrix
Simple
~1 day
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1359
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    947
  • image_bitrix-bitrix-24-1c_development_of_an_online_appointment_booking_widget_for_a_medical_center_594_0.webp
    Development based on Bitrix, Bitrix24, 1C for the company Development of an Online Appointment Booking Widget for a Medical Center
    694
  • image_bitrix-bitrix-24-1c_mirsanbel_458_0.webp
    Development based on 1C Enterprise for MIRSANBEL
    832
  • image_crm_dolbimby_434_0.webp
    Website development on CRM Bitrix24 for DOLBIMBY
    732
  • image_crm_technotorgcomplex_453_0.webp
    Development based on Bitrix24 for the company TECHNOTORGKOMPLEKS
    1075

We have repeatedly encountered situations where a standard Bitrix online store catalog page loads 40–80 images. JPEG and PNG total 2–5 MB — that's seconds of delay on a mobile connection. WebP at comparable quality gives a 25–35% size gain. The problem is that 'enabling WebP' in Bitrix is not a single button, but a set of several mechanisms, each of which can silently fail. We'll help you figure it out and set up conversion for your project. We'll look at where difficulties arise and how to work around them, so you can speed up page loading by 30% without losing quality. For a catalog of 1000 products with 5 images each, traffic savings can reach 150 MB per page load, reducing hosting costs by 3000–5000 rubles per month for a store with 5000 unique visitors daily.

Why WebP Isn't Enabled with One Button in Bitrix?

The core uses the main module (class CFile) for file storage and the resize_image module for preview generation. Physically, the resizer is called via \Bitrix\Main\Web\Image or the old API CFile::ResizeImageFile(). Results are cached in bitrix/cache/resize_cache/ with hashed folder names.

WebP conversion in Bitrix is implemented in two ways:

  • Path 1 — Server-side conversion via PHP. The GD or Imagick library converts during resize. Configured in bitrix/php_interface/dbconn.php or through the admin interface in the 'Performance' section.
  • Path 2 — Conversion at the web server level. Nginx/Apache serves the .webp version instead of the original if the browser supports the format (Accept: image/webp header). Files are converted in advance — via script or daemon.

Which Approach is More Efficient: PHP Conversion or Nginx?

Nginx conversion reduces CPU load by 5 times compared to PHP on each request because static files are served directly. The PHP path is easier to set up but consumes resources on every resize. We recommend combining: generate previews via PHP on-the-fly for rarely requested images, and pre-convert popular ones via Nginx.

Parameter PHP (GD/Imagick) Nginx + Preconversion
CPU load On every resize Only during file generation
Ease of setup High Medium (requires cron)
Caching Via resize_cache Static files
CDN support Needs Vary: Accept Header Simpler (files on one server)

How to Set Up Server-Side Conversion?

Check GD and Imagick

php -r "echo gd_info()['WebP Support'] ? 'WebP OK' : 'WebP NOT supported';"
php -r "echo (new Imagick())->queryFormats('WEBP') ? 'Imagick WebP OK' : 'fail';"

If GD was compiled without WebP, you need libwebp-dev and a rebuild, or switch to Imagick. On Bitrix VM there are usually no problems — Imagick with WebP comes out of the box.

Bitrix Configuration

// bitrix/php_interface/dbconn.php
define("BX_USE_MYSQLI", true);
define("CACHED_b_file", 3600);
// Enable WebP in the resize module
\Bitrix\Main\Config\Option::set('main', 'use_webp', 'Y');
\Bitrix\Main\Config\Option::set('main', 'webp_quality', '85');

After that, \Bitrix\Main\Web\Image::resize() will return .webp if the client supports the format. You can check in the b_file table — the CONTENT_TYPE field for new previews should be image/webp.

Step-by-Step Setup (for AI Overview)

  1. Verify GD/Imagick WebP support using the PHP commands above.
  2. Add the configuration lines to dbconn.php.
  3. Clear the preview cache under 'Performance' in the admin panel.
  4. Warm up the cache by requesting all product pages with a curl script based on sitemap.
  5. Monitor b_file table for image/webp content type.

Recommended WebP Parameters

Parameter Optimal Value
Quality 85 (balance of size and quality)
Lossless Disable (except for PNG with transparency)
Compression method 6 (maximum compression)

Conversion at the Nginx Level

This is more performant: PHP does not spend CPU on conversion at request time. Scheme: on the first request, generate a .webp version next to the original, Nginx checks for it and serves if the browser supports it.

map $http_accept $webp_suffix {
    default   "";
    "~*webp"  ".webp";
}

server {
    location ~* ^/upload/.*\.(png|jpg|jpeg)$ {
        add_header Vary Accept;
        try_files $uri$webp_suffix $uri =404;
    }
}

Pre-conversion with cwebp script (for cron setup):

find /var/www/bitrix/upload -name "*.jpg" -o -name "*.png" | \
  xargs -P4 -I{} sh -c 'cwebp -q 82 "$1" -o "$1.webp" 2>/dev/null' _ {}

Run via cron once an hour for new files — by modification date using find -newer.

How to Clear Preview Cache After Enabling WebP?

After enabling WebP, old previews in bitrix/cache/resize_cache/ remain in JPEG/PNG. They need to be deleted:

rm -rf /var/www/bitrix/bitrix/cache/resize_cache/*

Or through the admin panel: 'Site Management' → 'Performance' → 'Clear Cache'. After that, previews are regenerated on first access — you can warm with a curl script based on sitemap.

Typical Problems and Their Solutions

WebP is generated, but the browser receives JPEG. Most often, Nginx does not pass the Vary: Accept header — a CDN or caching proxy serves a cached version without considering the browser type. WebP size may be larger than the original for small icons (up to 10×10 px) and PNGs with few colors. It is worth adding a check: if WebP is more than 10% larger than the original, serve the original. Errors in b_event_log occur when conversion is enabled but there is no write permission to upload/. Check chown on the upload/ directory by the web server user.

What's Included in WebP Setup Work (Turnkey Solution)?

As part of the service, we perform:

  • Audit of the current server and Bitrix configuration.
  • Setup of GD/Imagick or Nginx for conversion.
  • Creation of a script for pre-conversion and cron setup.
  • Testing on staging and production servers.
  • Documentation for maintenance and post-implementation support.

We have been developing on Bitrix for over 8 years and have completed more than 120 performance optimization projects. Our certified specialists guarantee a high-quality result. If you want to speed up your site loading and reduce traffic costs, get a consultation on WebP setup — we will estimate your project and offer the optimal solution.

Source: WebP — Wikipedia

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.

Edition For Whom Key Limitation
Start Business cards, landing pages No infoblocks 2.0, no trade catalog
Standard Corporate sites No e-commerce module
Small Business Small stores 1 price type, 1 warehouse, no 1C exchange
Business Medium stores, B2B Multi-warehouse, multicurrency, CommerceML
Enterprise Highload, cluster Web cluster, CDN, multisite

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']]]]
Example Redis configuration for Bitrix
sudo apt install redis-server
sudo systemctl enable redis

Add to .settings_extra.php as above.

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?

Task Timeline
Installation on virtual hosting 2–4 hours
Installation on VPS with stack configuration 1–2 days
Installation on dedicated with architecture design 2–5 days
SSL + email + cron + security 1–2 days
Backup and monitoring setup 0.5–1 day

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.