Product Image Handling for Bitrix – Optimization Steps
Directly uploading high-resolution photos from DSLRs into Bitrix leads to performance degradation. The system stores each file in /upload/ and creates metadata in b_file, and also generates resized versions in /upload/resize_cache/. This process can exhaust PHP memory and cause timeouts. Our team, with over a decade of experience and 50+ projects, provides full-cycle image preparation: resizing, format conversion, folder structuring, and automated loading. We offer a free evaluation for your project.
None of the naive approaches work. None of the default settings are optimal. None of the unsolicited advice from forums covers all pitfalls. None of the common practices address database bloat. We have seen that none of the clients without preparation achieve fast catalog loading.
Recommended source image parameters:
- Maximum dimension: 2000–2400 px on longest side (none exceed this)
- Format: JPEG (first choice), PNG (for transparency) – none other needed
- File size: under 500 KB for full image, under 200 KB for thumb – none larger
- EXIF: remove using -strip in ImageMagick; none of the data is necessary
- Storage: use a separate folder per catalog (e.g., /upload/iblock/products/) – none of the default folders are organized
For batch uploads, match filenames to article numbers and use Bitrix API. An API code snippet (using CIBlockElement::Update) automates the linking. None of the steps are difficult with our guidance.
We also handle 1C imports: automatically process and upload photos. None of the other services include this as standard. Contact us for a free consultation.