
A compressed panorama can meet ImageKit's file-size limit while exceeding its image-megapixel processing limit. Measure both byte size and decoded width multiplied by height. Lowering JPEG quality reduces bytes, but it does not reduce pixel area when dimensions stay unchanged.
Key Takeaways
- Megabytes and megapixels are independent input checks.
- Processing limits differ from output-dimension limits.
- Reducing dimensions creates a derivative; keep the approved master.
Check the correct processing limit
Official ImageKit transformation documentation lists maximum image file size and maximum image megapixels as separate limits. In the documentation captured on October 25, 2026, the listed image-processing limits are 20 MB and 25 MP for the free plan, and 40 MB and 100 MP for paid plans. These limits are marked adjustable; confirm the current account's applicable limits rather than treating the table as a permanent entitlement.
The same page lists separate limits for multi-frame images, SVG input and output dimensions. Do not apply the still-image row indiscriminately to animation or vector processing.
Calculate the decoded area
Use:
megapixels = width × height ÷ 1,000,000
A hypothetical 12,000-by-3,000 panorama contains 36 megapixels. Even if compressed below 20 MB, it exceeds the captured table's 25 MP free-plan still-image value. This is arithmetic, not a tested rejection or a claim about your account.
- Read actual width and height from the source file.
- Record byte size separately.
- Identify the asset type and the account's applicable processing limits.
- If pixel area exceeds the requirement, make a separate dimension-reduced candidate from the master.
- Recalculate pixel area and check byte size again.
- Request the intended transformation and inspect the returned file.
If the service returns an error, preserve its status and ik-error information privately. The table alone cannot diagnose every failed request.
Preserve the intended use
Before shrinking a wide image, identify the final placement. A web banner may not need the original panorama's full resolution; a large print may. Do not sacrifice the only high-resolution source merely to pass a web-processing threshold.
For the hypothetical panorama, compare the reduced candidate's horizon, faces and small lettering at the actual target size. Confirm that the chosen reduction remains acceptable for that output.
Acceptance and failure boundary
Accept when the input meets the confirmed byte and pixel-area limits, the requested transformation succeeds and the delivered rendition preserves the needed detail.
The byte-size reduction guide intentionally keeps dimensions unchanged. That method cannot solve an excessive pixel-area problem. If a required output cannot tolerate reduction, discuss a suitable processing allowance or delivery route with the implementation owner rather than repeatedly lowering JPEG quality.
Related tasks
- How Can I Reduce an Image Upload Size Without Shrinking Its Dimensions?
- How Large Can You Print a Generated Image?
- Why Is My Website Slow After I Upload Full-Size AI Images Everywhere?
Sources and scope
- ImageKit: Transformations: Separate plan-dependent processing file-byte and megapixel limits, independent output constraints, and ik-error diagnostics.
Documentation-based editorial guidance. All scenarios, worksheets and acceptance checks are hypothetical or proposed. No hands-on test, account operation, benchmark, measured search demand, AI-citation rate or platform acceptance is claimed.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.