Register WordPress Image Sizes Without Editing PHP

• WordPress themes and plugins can register additional image dimensions with add_image_size(), but that normally places an ongoing media requirement inside code. If a site needs a 400×300 card image, a 1920×600 hero crop, or a dedicated social-sharing size, a developer has to add or maintain that registration somewhere in the theme or plugin stack.
• Custom Image Sizes moves that configuration into WP PowerSuite. You define the size name, width, height, and crop behavior through the module, and WP PowerSuite registers the resulting size so new eligible uploads are processed through the normal WordPress media pipeline. This keeps the requirement visible to site administrators and independent of theme file edits.

Create Sizes That Match the Design

• Image dimensions should reflect the components that actually exist on the website. A landscape article card and a square team profile should not necessarily reuse the same source crop simply because WordPress already provides medium and large sizes.
• The module lets you create up to 20 custom definitions with dimensions up to 4096 pixels. At least one dimension must be greater than zero. Setting one side to zero follows WordPress's normal proportional-scaling behavior, while enabling Crop produces a fixed crop when the source image is large enough.
• Built-in presets for OG 1200×630, Hero 1920×600, Card 400×300, and Square 600×600 make common scenarios faster, while ratio helpers calculate 16:9, 4:3, or 1:1 dimensions from an 800-pixel starting width.

Avoid Naming Conflicts With Themes and Plugins

• Image size names are global inside WordPress. If a theme already registers a size and another component registers a different size under the same name, the final behavior can become difficult to reason about.
• WP PowerSuite snapshots the image sizes registered by the theme and other plugins before adding its own definitions. The settings interface can then warn when a custom size name collides with an existing additional size. WordPress's reserved core names such as thumbnail, medium, medium_large, and large are blocked from custom creation.
• This gives developers visibility before a conflict becomes part of the upload pipeline rather than discovering it later through missing or unexpectedly cropped files.

New Sizes Affect New Uploads

• Registering a new image size tells WordPress what to generate during future image processing. It does not retroactively create that file for images already stored in the Media Library.
• Deleting a custom definition also stops future generation but does not remove files that were created for older attachments. Registration, regeneration, and filesystem cleanup are separate operations, which keeps the module predictable and avoids destructive changes when a size is edited or removed.

Coordinate Custom Sizes With Thumbnail Generation

• Custom Image Sizes defines which dimensions exist. Disable Thumbnail Generation controls which registered dimensions WordPress is allowed to create on new uploads. Those are complementary controls rather than contradictory settings.
• If a custom size remains registered but is selected in Disable Thumbnail Generation, WordPress still knows about the size but its intermediate file is skipped during image metadata generation. WP PowerSuite surfaces this relationship so an administrator is less likely to assume a custom size is broken when it has intentionally been disabled.
• Once files have been generated, Image Sizes Panel can be used to inspect the actual available URLs and dimensions for an attachment, which is useful when confirming a custom media setup.

Regenerate Existing Attachments When Your Size Strategy Changes