What this checklist covers
This is practical guidance for the stated workflow. It does not replace checking the output for your own document and use case.
1. Preserve shape before worrying about file size
A resize should not stretch a logo, screenshot, or interface asset into a different shape. NetroDoc calculates the missing dimension from the source aspect ratio. If you provide both width and height, the image fits inside that bounding box rather than being forced to exactly match both numbers.
This is different from cropping. A 1200 × 800 source placed inside an 800 × 800 bounding box will fit proportionally; it will not become a distorted square.
- Use width only when horizontal size is the real constraint.
- Use height only when vertical size is the real constraint.
- Use width and height together when both are maximum limits.
2. Understand what downscaling removes
Downscaling creates fewer output pixels, so some source detail must be combined or discarded by the resampling step. PNG then stores those new pixels losslessly, but the resized image is not pixel-identical to the larger source.
That is normally acceptable when the destination never displays the original size. Inspect small text, one-pixel lines, icons, and diagrams after resizing because those details are more sensitive than a photograph.
- Keep the original as the master file.
- Judge sharpness at the size where the image will actually be used.
- Avoid repeated resize cycles; export again from the original instead.
3. Treat upscaling as enlargement, not restoration
NetroDoc allows larger output dimensions, but interpolation cannot reconstruct real detail that was never captured in the source. A small 300-pixel logo can be made 1200 pixels wide, yet edges may look softer because the new pixels are estimates.
If a larger source exists, use it. Upscaling is best treated as a compatibility step when a system requires minimum dimensions, not as a way to recover lost resolution.
- Prefer the highest-quality original available.
- Do not promise more detail simply because the pixel count increased.
- Compare the enlarged result at 100% zoom before publishing it.
4. Keep transparency and choose the next step separately
Resize PNG retains supported alpha transparency and rejects animated PNG files instead of silently discarding extra frames. After resizing, use Compress PNG when you want lossless optimization or PNG to WebP when a modern delivery format fits the destination.
For many images, Batch Image Studio or Batch Image Resizer can apply a shared dimensional rule. If the images will later become a PDF, resize them before combining only when smaller dimensions are actually useful for the document workflow.
- Resize first when dimensions are the problem.
- Compress after resizing when PNG file size still matters.
- Convert format only when the destination supports and benefits from it.
Temporary processing and privacy
Resizing uses temporary processing storage. The visible image content remains visible in the resized output, and resizing is not a privacy or redaction step.
Read the Privacy Policy →Troubleshooting
The resized PNG looks blurry
Return to the original and use a less aggressive downscale, or avoid upscaling a source that is already too small.
The result is not exactly the width and height I entered
When both dimensions are supplied, they form a bounding box so the original aspect ratio can be preserved.
I need to resize many PNG files
Use Batch Image Studio or Batch Image Resizer, test the rule on a small sample, and inspect the ZIP output before replacing originals.
Editorial note
NetroDoc practical guides explain a specific file workflow and link to the tools that carry out each step. They avoid presenting a general recommendation as a guarantee for every file.