
In ImageKit, f-orig keeps the original format after processing; it does not promise the original file bytes. Use orig-true when the requirement is to deliver the original file as is. Lossless compression and an explicit output format are additional choices, each answering a different delivery question.
Key Takeaways
- Original format, original bytes and lossless encoding are different contracts.
orig-truecauses other transformation parameters to be ignored.- A lossless request can still negotiate WebP unless PNG is explicitly selected.
Choose the contract from the recipient's need
Official ImageKit optimization reference defines f-orig as leaving the image in its original format after processing. Resizing or other requested processing can still occur.
Its PNG-compression section says lo-true can deliver losslessly compressed WebP in Chrome; adding f-png selects losslessly compressed PNG. Lossless therefore does not mean “keep the PNG container,” much less “return my exact uploaded file.”
The core-delivery reference separately defines orig-true for original-file delivery and says other transformation parameters supplied with it are ignored.
Create a three-row delivery record
| Requirement | Candidate choice | Check |
|---|---|---|
| Processed image in its source format | f-orig | Format plus intended processing |
| Processed lossless PNG | lo-true,f-png | Actual PNG and visual result |
| Original file as is | orig-true | File identity against retained source |
- Preserve the exact uploaded source in controlled storage.
- Ask whether the receiver needs appearance, format compatibility or file identity.
- Build one candidate for that requirement without mixing conflicting expectations.
- Download the actual response.
- Identify its format and dimensions, then compare appearance.
- Where byte identity is required, compare a trusted cryptographic checksum with the retained source.
A matching checksum establishes file identity for that comparison. It does not establish editorial quality, authorship or rights.
A hypothetical transparent logo handoff
A client needs a lossless PNG for a desktop layout and the untouched upload for an archive. The proposed package keeps those outputs distinct. A WebP rendition may be acceptable for the website while still failing the client's requested PNG contract.
If orig-true is combined with a resize, do not assume both requests will be honored. The documented precedence means the transformation is ignored.
Acceptance and limits
Accept when each delivered file matches its stated role and the receiver can open the required format. Review transparent edges and fine lettering in the processed rendition.
The approved-file handoff record helps label these separate outputs. Avoid using “original” without stating whether it means original format or original file. No download, compression benchmark or checksum result is claimed here.
Related tasks
- JPEG, PNG or WebP: Choose a Photo Export Format
- How Can I Reduce an Image Upload Size Without Shrinking Its Dimensions?
Sources and scope
- ImageKit: Image optimization: f-orig preserves format after processing; lo-true can still deliver WebP while f-png explicitly selects PNG; separate output-format and compression controls.
- ImageKit: Core delivery features: orig-true delivers the original file as is and ignores other transformation parameters.
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.