When the Image Is the Bottleneck: Preparing Large Image Files for Skavio File Toolbox
Large image files create two separate planning problems: the receiving workflow may not accept the format, and the upload may exceed a batch limit when files are assembled. Skavio File Toolbox supports these image inputs: JPG/JPEG, PNG, WEBP, BMP, TIF/TIFF, GIF, HEIC/HEIF and AVIF. It can output JPG, PNG, WEBP or PDF. The documented conversion scope covers format conversion; automatic resizing and compression are not listed as File Toolbox features. The practical approach is preparation-first: inventory the files, convert only what the destination needs, batch within the published limits, and treat the live backend quote as the cost authority.
Inventory the image set before you touch the upload field
Start with a working list: filename, source format, actual file size, intended recipient, required output format and whether the original must remain untouched. Format support is not the same as size fit. A HEIC photo from a phone or a TIF scan may be supported as input, but the receiving workflow may still expect a different format. For PDF sources, note both page count and file size; for image-only sources, record the real file size because that is the relevant file-work basis. Keep an untouched original in your own storage and do not treat a processed output as your only archive copy.
- Record each file's actual extension and size rather than relying on a camera or phone label.
- Separate two questions: does the receiver need a different format, and does the file need to be smaller? Format conversion is supported; automatic resizing and compression are not documented File Toolbox features.
- Keep the original source file in your own storage before uploading a copy for conversion.
Choose the output the receiving workflow can use
The verified image output set is JPG, PNG, WEBP and PDF. That is a short menu, not a quality ranking. Choose the format the recipient has asked for, or the one your document workflow can open. A review packet may call for PDF; an image workflow may call for JPG, PNG or WEBP. Do not assume conversion will reduce file size, improve resolution or preserve every property of the source unless you have checked the output yourself. For multi-page PDF-to-image work, the result is delivered as a ZIP, so plan to inspect the contents rather than treating it as a single image.
- Match the output to a stated requirement, not to a guess about which format is generally preferable.
- A format conversion is not a substitute for checking that the output remains readable and complete.
- If the only problem is size rather than format, use a separate preparation step outside File Toolbox and keep the original intact.
Batch the upload around published limits and a live quote
Published limits in the Skavio Processing API documentation list 100 upload files and 500 MB total per upload, 2 GB company source storage, seven-day retention, 100 queued company jobs, four active company jobs and three unfinished web jobs. Treat those as planning numbers, then confirm the live web interface before relying on them for a web job. For large images, count by total megabytes as well as file count; ten 45 MB images already approach 450 MB. The reviewed file-work pricing is 3 credits per started 25 MB or 3 credits per started 10 PDF pages, using the larger basis per source. The live backend quote is authoritative for the final job price. A successful job settles once, and a permanent failure releases the credit reservation.
- Build batches below the 500 MB total and 100-file upload envelope, leaving room for retries and related outputs.
- Do not use the processing service as an archive: published retention is seven days and company source storage is 2 GB.
- Get the live quote before committing a large batch; do not extrapolate a per-image cost from one example.
- For PDF sources, compare both size units and page units. For image-only inputs, start from file size and let the live quote decide.
Verify outputs, then move them into your own record
After conversion, open a sample output, confirm the file extension and check that the content matches the source you intended to send. For ZIP delivery from a multi-page PDF-to-image job, inspect the page count and filenames. Standard File Toolbox conversions run locally or through Skavio Worker Fabric rather than a paid AI API for normal processing; that is an architecture note, not a security certification. Actual processing depends on file size, format, queue and service availability, so avoid treating one run as a universal speed or quality benchmark. Large images can contain personal or confidential content, so review what you upload and follow your own data-handling policy.
- Open at least one converted result and check that it matches the intended source content and output format.
- For multi-page PDF-to-image work, verify the ZIP contains the expected pages in sequence.
- Download completed outputs promptly and store them in an approved location; the processing service is not a permanent archive.
- Review sensitive images before upload and keep any necessary internal approvals outside the conversion tool.