Imagify

Entry point

The plugin starts from imagify.php. It defines global constants, includes the Composer autoloader, then hooks the imagify_init() function on plugins_loaded.

Registered Service Providers

Initialisation sequence

// 1. plugins_loaded
imagify_init()
  └── include vendor/autoload.php
  └── new Imagify\Plugin()
        └── load config/providers.php        // register services
        └── boot Options, Data, Auth
        └── boot Auto-Optimization
        └── (admin only) boot Settings, Views, Imagifybeat
  └── do_action('imagify_loaded')

Compression levels

Automatic optimisation on upload

When the auto_optimize option is enabled, the Imagify_Auto_Optimization class hooks into wp_generate_attachment_metadata. Each uploaded image is optimised immediately, along with all its thumbnails.

Backup system

• Enabled via the backup option.
• The original file is copied before any compression.
• Backup directory is filterable via imagify_backup_directory.
• Restoring puts the original back in place and removes optimisation metadata.

Large image resizing

• Option resize_larger: when enabled, images exceeding resize_larger_w pixels wide are resized.
• Default value: 2560 px (aligned with the WP filter big_image_size_threshold).

Thumbnail management

All sizes registered in WordPress are optimised. Sizes can be excluded via the disallowed-sizes blacklist in the settings.

Optimisation statuses

Metadata stored per attachment

// Attachment post meta
_imagify_status          // 'success' | 'already_optimized' | 'error' | 'pending'
_imagify_data            // JSON — full optimisation results
_imagify_level           // Level used (0, 1, 2)
_imagify_next_gen_done   // Boolean — next-gen versions generated

File generation

After optimisation, Imagify can generate WebP and/or AVIF versions of each image. The optimization_format option controls this behaviour:

Display method: <picture>

Class: Imagify\Picture\Display. The plugin starts an output buffer on template_redirect, scans the generated HTML, and replaces each <img> with a <picture> block containing <source> elements pointing to the WebP/AVIF files.

<!-- Before -->
<img src="photo.jpg" alt="...">

<!-- After transformation -->
<picture>
  <source srcset="photo.avif" type="image/avif">
  <source srcset="photo.webp" type="image/webp">
  <img src="photo.jpg" alt="...">
</picture>

Display method: Server rewrite

Class: Imagify\Webp\Display. Rather than altering the HTML, rules are written directly into .htaccess (Apache) or web.config (IIS). The server automatically serves WebP if the browser accepts it (Accept: image/webp).

Bulk architecture

The Imagify\Bulk\Bulk class orchestrates bulk optimisation. It relies on ActionScheduler (bundled library) to create asynchronous jobs processed in the background.

Execution flow

// Trigger (UI or CLI)
imagify_bulk_optimize (AJAX)  // or wp imagify bulk-optimize
  └── Imagify\Bulk\Bulk::run()
        └── ActionScheduler::enqueue(imagify_optimize_media)
              └── Imagify\Job\MediaOptimization::execute()
                    └── Imagify\Optimization\File::optimize()
                          └── Remote Imagify API

Bulk next-gen version generation

The AJAX action imagify_missing_nextgen_generation and the ActionScheduler hook imagify_convert_next_gen allow generating WebP/AVIF versions for all already-optimised images whose next-gen files are missing.

Principle

Custom folders allow optimising images located anywhere on the server (themes, plugins, custom directories). They are indexed in two dedicated MySQL tables.

Available features

• Scan: automatic detection of new images in configured folders.
• Individual or bulk optimisation via the same ActionScheduler system.
• Re-optimisation: if the source file has been modified (detected by hash).
• Restore from backup.
• Cron synchronisation to detect modified/deleted files.

Main classes

// Database access
Imagify_Files_DB        // CRUD on wp_imagify_files
Imagify_Folders_DB      // CRUD on wp_imagify_folders
Imagify_Files_Scan      // Filesystem scan

// Context
Imagify\Context\CustomFolders

AJAX actions (wp_ajax_*)

Admin-Post actions (admin_post_*)

Imagifybeat

Real-time update system (analogous to WordPress Heartbeat). Hook: wp_ajax_imagifybeat. Interface data (nonces, statuses) is refreshed periodically via AJAX polling, configurable by filter.

The plugin automatically detects NextGEN Gallery and activates a dedicated context (Imagify\Context\NGG).

Plugins

WooCommerce detail

On variable product pages, WooCommerce dynamically replaces the main image. Imagify fixes the wp-post-image class on generated <picture> tags to maintain compatibility with WooCommerce's image-switching mechanism.

Hosts

ActionScheduler

The ActionScheduler library is bundled in /inc/Dependencies/ActionScheduler/. It manages asynchronous optimisation jobs:

• imagify_optimize_media — Processes a single optimisation job.
• imagify_convert_next_gen — Generates next-gen versions.

All jobs are cleaned up when the plugin is deactivated.

Main actions

Main filters

Available plans

Data exposed by Imagify\User\User

quota                        // Total monthly quota (MB)
consumed_current_month_quota // Quota consumed this month (MB)
extra_quota                  // Imagify byte pack (MB)
extra_quota_consumed         // Pack consumed (MB)
next_date_update             // Quota reset date
is_active                    // Account active

Cache

User data is cached in a WordPress transient (imagify_user_cache) for 5 minutes. The cache can be manually cleared via the AJAX action imagify_delete_user_data_cache.

Internal state reset

AJAX action: imagify_reset_internal_state (requires the manage capability). This one-click tool unblocks the bulk optimiser when it gets stuck in an inconsistent state.

What gets cleaned up