Compression • Conversion • Remove Metadata
Image Processing Reference
Guides for every Pictobank workflow.
Learn how compression, resizing, conversion, enhancement, metadata cleanup and Pipeline Builder fit into practical image and document preparation.
Resize • Crop • Rotate / Flip
Auto Enhance • Brightness / Contrast • Saturation
Pipeline Builder • Batch recipes • ZIP exports
Optimize
Prepare smaller, cleaner files for publishing and delivery.
CompressionConversionRemove Metadata
Edit
Adjust dimensions and orientation before export.
ResizeCropRotate / Flip
Enhance
Use practical image adjustments without restoration claims.
Auto EnhanceBrightness / ContrastSaturation
Build
Turn repeated file preparation into a reviewable workflow.
Pipeline BuilderBatch recipesZIP exports
Tool Guides
Open the guide inside each tool page
Each guide stays next to the matching Pictobank tool so settings, examples, and review steps are easy to compare.
Image Compression Guide
Learn how file size, dimensions, format, and compression settings affect everyday image delivery.
Open guideImage Resizing Guide
Choose dimensions, aspect ratios, and output sizes for web, social, ecommerce, and documents.
Open guideImage Conversion Guide
Compare JPEG, PNG, WebP, AVIF, and practical output choices for compatibility and size.
Open guideImage Enhancement Guide
Use auto enhance, brightness, contrast, saturation, sharpen, grayscale, rotate, flip, and light denoise carefully.
Open guideRemove Metadata Guide
Understand hidden file details, clean exports, color-profile handling, and why metadata cleanup is not redaction.
Open guidePipeline Builder Guide
Build repeatable recipes for compression, resize, conversion, enhancement, and metadata cleanup.
Open guideUse it when
Example decisions
Short examples for choosing the right Pictobank workflow.
Use compression when a product image is too large for email, web upload, or fast page loading.
Build a pipeline when you repeat the same Enhance, Resize, Convert, and Clean steps every week.
Plain-language legend
Quick terms
Concise definitions for common terms used across these guides.
Why it matters: It is widely supported but usually uses lossy compression.
Example: Use JPEG for broad compatibility when transparency is not needed.
Why it matters: It is useful for graphics and transparent assets but can be large for photos.
Example: Use PNG when a logo or screenshot needs transparent areas.
Why it matters: It often makes smaller web files while keeping broad browser support.
Example: Use WebP for product grids, landing pages, and blog images.
Why it matters: It can create smaller files but may take longer to encode.
Example: Use AVIF when size matters more than processing speed.
Why it matters: It can make files much smaller but should be reviewed visually.
Example: Use a less aggressive preset if product detail starts to soften.
Why it matters: It usually saves less space but can be safer for graphics and reference files.
Example: Use lossless-style output when small visual changes are unacceptable.
Why it matters: Dimensions often affect file size and whether an image fits a destination.
Example: Resize a 4000px image to 1200px when the website only displays 1200px.
Why it matters: Cropping can improve framing but permanently changes what appears in the export.
Example: Crop a product photo to a square marketplace frame before compression.
Why it matters: Formats affect compatibility, transparency, quality, and file size.
Example: Convert PNG to WebP for a web page after checking transparency needs.
Why it matters: It can include location, camera, author, software, or timestamp details.
Example: Remove metadata before sharing a phone photo publicly.
Why it matters: It helps apply the same steps to many files consistently.
Example: Enhance, resize, convert, and clean metadata every week with one recipe.
Practical guide questions
Why do guide pages avoid guarantees?
Image results vary by source file and settings, so guides explain decision patterns instead of promising one perfect output.
When should I resize before compressing?
Resize first when the image dimensions are larger than the final destination needs.
When should I clean metadata?
Clean metadata before public, client-facing, or link-based sharing when hidden file details are not needed.
When should I build a pipeline?
Build a pipeline when the same preparation steps repeat across folders, campaigns, listings, or recurring batches.
Ready to apply these guides?
Open the workspace, upload a supported file, and choose the workflow that fits your task.