CartVisualCreate account

When can Claid combine JPEG decompression with upscale, and when must polish be omitted?

Use Claid decompress for compression artifacts, upscale when more pixels must be rendered, and polish only when a sharper finishing candidate is appropriate and its target falls within the documented 16 MP limit. Decompress and upscale can be configured together; neither is enabled automatically. Choose an upscale method by source type, then treat product lettering or texture not established by the source as unresolved.

Published · By CartVisual editorial team

Separate compression damage from enlargement

Claid's decompression and upscaling controls address different problems. Decompress targets artifacts introduced by image compression; upscale renders additional pixels. Increasing the output dimensions does not itself establish that compression damage has been resolved.

For decompression, choose moderate when the task is ordinary JPEG artifact removal, strong when more aggressive artifact treatment is justified, or auto when the request should detect and remove JPEG artifacts if needed. Decompression is off unless configured.

Upscale is off by default. Claid lists smart_enhance for small, lower-quality product images and smart_resize for high-quality images and photos with barely readable text. Its ecommerce tutorial sends smart_enhance in JSON but names smart_resize in the explanation. Use the Restoration reference and record the value you actually send.

Claid explicitly allows decompression to be used with upscale. The useful pre-submission question is therefore whether the source has compression artifacts, insufficient delivery dimensions, or both. Do not add an upscale operation merely because decompression is needed.

Configure the required operations without adding polish automatically

The following illustrative fragment assumes that the original photo is high quality and its small label text is still readable with magnification. The source class points to smart_resize. For a small, low-quality product source, start with the method documented for that source class instead. Include decompression only when JPEG artifacts are present.

Polish is separate. Claid describes it as redrawing parts of an image to make them sharper while retaining the original structure. It may be used alone or with upscale, but it is not a replacement for decompression when JPEG artifacts are the diagnosed defect.

Before requesting polish, calculate the intended target pixel count. The written documentation specifies a maximum target size of 16 MP. Its accompanying examples are internally inconsistent with a strict 16-million-pixel reading: 4096 × 4096 equals 16,777,216 pixels, and 5000 × 3500 equals 17,500,000 pixels. Do not use those examples to assert eligibility above the written limit. Choose an unambiguously smaller target or obtain current clarification.

{
  "operations": {
    "restorations": {
      "decompress": "auto",
      "upscale": "smart_resize"
    },
    "resizing": {
      "width": "200%",
      "height": "200%"
    }
  }
}

Make the requested dimensions an eligibility check

Calculate the proposed dimensions before adding polish. A 3000 × 3000 source enlarged to 200% in each dimension requests 6000 × 6000 pixels, or 36 MP. That is beyond the documented polish ceiling. Omit polish from that configuration rather than assuming the service will silently resize, skip, or downgrade it.

The accepted request configuration and the eventual downloaded image are separate evidence. Record the operation fields, requested dimensions, actual dimensions if produced, and the source used to verify lettering or physical detail. The existing upscale-evidence guide addresses whether newly sharp merchandise detail can be trusted; this guide addresses operation compatibility and eligibility before submission.

Illustrative decision: a compressed supplier photograph needing enlargement

The merchant has the original, sharp 3000 × 3000 supplier photograph. In the authorized JPEG copy for this job, the label remains barely readable at native size, and small compression blocks appear in its blank surround. The placement calls for a 6000 × 6000 canvas. The seller must address both the JPEG artifacts and the placement size.

The planned request combines decompress auto and upscale smart_resize with 200% resizing. The target is 36 MP, above the documented polish ceiling. Omit polish. A replacement photo that already meets the placement size and has no compression artifacts needs neither of the two restoration operations for this brief.

The next action is to validate the intended request and dimension requirements before any authorized processing. If the label is unreadable in the genuine source, obtain approved lettering evidence rather than assuming enlargement will recover it.

Where CartVisual fits

The browser-local checklist can support manual comparison of an externally restored image with its source. It does not execute Claid restoration or validate API configuration.

See the current CartVisual workflow and its limitations

Source and evidence scope

Prepared by the CartVisual editorial team with AI assistance. Competitor behavior is documented rather than independently executed for this guide.

Claid: Restorations

Official source snapshot checked .

Claid: E-commerce

Official source snapshot checked .

The Restoration reference documents the operations, named methods, combinations, and the written 16 MP polish limit. Its dimensions conflict with that limit. The ecommerce tutorial supplies the separate mismatch between code and explanation. The worked example is a configuration plan.

Related decisions

Browse ecommerce creative workflows