Image processing and local state
Your selected picture stays in the browser
this part of the page begins with a concrete purpose. Supported images are decoded, resized, encoded, or padded by code on the current device. The MVP has no account system and no server endpoint intended to receive the selected image. Keeping the purpose visible beside the controls makes the next choice easier to understand and repeat.
A useful result from this practical guidance follows a short, reviewable sequence. Close or refresh the page to clear temporary working state, then manage downloads on your device. The MVP has no account system and no server endpoint intended to receive the selected image. Check the displayed measurements before saving or submitting the output somewhere else.
The boundary around the current workflow matters as much as the main feature. Browser extensions, device backups, or software outside our control may handle local files differently. Supported images are decoded, resized, encoded, or padded by code on the current device. Pixels, file bytes, and newly recovered visual detail are not interchangeable ideas.
For predictable work, keep this documented choice measurable from start to finish. Close or refresh the page to clear temporary working state, then manage downloads on your device. Browser extensions, device backups, or software outside our control may handle local files differently. Compare the source and preview instead of relying on a vague promise about quality.
Website delivery and limited logs
Data needed to serve and protect a page
this part of the page begins with a concrete purpose. Hosting infrastructure may receive IP address, user agent, requested URL, time, and response status. These records can support delivery, abuse prevention, debugging, and aggregate reliability analysis. Keeping the purpose visible beside the controls makes the next choice easier to understand and repeat.
A useful result from this practical guidance follows a short, reviewable sequence. Avoid entering personal information in filenames or feedback when technical measurements are sufficient. These records can support delivery, abuse prevention, debugging, and aggregate reliability analysis. Check the displayed measurements before saving or submitting the output somewhere else.
The boundary around the current workflow matters as much as the main feature. We do not describe ordinary page logs as image uploads and do not use them to reconstruct pictures. Hosting infrastructure may receive IP address, user agent, requested URL, time, and response status. Pixels, file bytes, and newly recovered visual detail are not interchangeable ideas.
For predictable work, keep this documented choice measurable from start to finish. Avoid entering personal information in filenames or feedback when technical measurements are sufficient. We do not describe ordinary page logs as image uploads and do not use them to reconstruct pictures. Compare the source and preview instead of relying on a vague promise about quality.
Advertising, cookies, and web technologies
A conditional notice for any future ad activation
this part of the page begins with a concrete purpose. The core image workflow does not require advertising identifiers or a paid processing API. If third-party advertisers, including Google, are enabled, they may use cookies and web beacons for ad serving under their own notices and consent requirements. Keeping the purpose visible beside the controls makes the next choice easier to understand and repeat.
A useful result from this practical guidance follows a short, reviewable sequence. Where required, we will present choices and update this policy before or when such advertising is active. If third-party advertisers, including Google, are enabled, they may use cookies and web beacons for ad serving under their own notices and consent requirements. Check the displayed measurements before saving or submitting the output somewhere else.
The boundary around the current workflow matters as much as the main feature. This conditional explanation does not claim that third-party advertising is currently enabled. The core image workflow does not require advertising identifiers or a paid processing API. Pixels, file bytes, and newly recovered visual detail are not interchangeable ideas.
For predictable work, keep this documented choice measurable from start to finish. Where required, we will present choices and update this policy before or when such advertising is active. This conditional explanation does not claim that third-party advertising is currently enabled. Compare the source and preview instead of relying on a vague promise about quality.
Your choices, retention, and policy changes
Control the browser and contact us
this part of the page begins with a concrete purpose. You can block or clear site storage, manage browser permissions, and delete downloaded results. Security or hosting logs may be retained only as reasonably needed for operations and legal obligations. Keeping the purpose visible beside the controls makes the next choice easier to understand and repeat.
A useful result from this practical guidance follows a short, reviewable sequence. Use the contact page for a privacy question without attaching sensitive pictures or identifiers. Security or hosting logs may be retained only as reasonably needed for operations and legal obligations. Check the displayed measurements before saving or submitting the output somewhere else.
The boundary around the current workflow matters as much as the main feature. Material changes to processing, storage, vendors, or advertising will require a corresponding policy update. You can block or clear site storage, manage browser permissions, and delete downloaded results. Pixels, file bytes, and newly recovered visual detail are not interchangeable ideas.
For predictable work, keep this documented choice measurable from start to finish. Use the contact page for a privacy question without attaching sensitive pictures or identifiers. Material changes to processing, storage, vendors, or advertising will require a corresponding policy update. Compare the source and preview instead of relying on a vague promise about quality.
What the browser actually does
IncreaseImages uses browser image APIs rather than a remote enhancement service. That distinction matters: the tool can resample pixels and re-encode a file, but it cannot recreate detail that the source never contained.
Published limits you can verify
- Three static input and output families are supported in this MVP: JPEG, PNG, and WebP.
- Each selected file is limited to 25 MiB before decoding; animated formats and unsupported containers are rejected.
- A generated result is limited to 32 megapixels and 8,192 pixels on either edge to reduce browser memory failures.
| Capability | Current boundary | What it means |
|---|---|---|
| Processing location | This browser | No image file is sent to an IncreaseImages server. |
| Pixel enlargement | Up to 4× per edge | A 2× edge scale creates four times as many pixels. |
| Output encoding | JPEG, PNG, WebP | Actual support is checked before a download is offered. |
Primary sources and method notes
MDN documents that Canvas can create a Blob in a requested image format and that image smoothing is used during scaling. The HTML standard defines these browser behaviors; our numeric limits above are product safeguards reviewed on the stated date. HTML Living Standard: Canvas.
MDN describes the core export step plainly:
MDN Web Docs, HTMLCanvasElement.toBlob()
The HTMLCanvasElement.toBlob() method creates a Blob object representing the image contained in the canvas.
- MDN: HTMLCanvasElement.toBlob()
- MDN: createImageBitmap()
- Limits and source links last reviewed: .
Questions before you resize
Does IncreaseImages upload my selected image?
The current MVP does not send selected image contents to an IncreaseImages image-processing server. Processing happens in browser memory, while ordinary page requests may still appear in hosting or security logs.
Does the site use cookies?
The core tool does not need a cookie to process an image. Hosting, preferences, consent tools, or future advertising may use storage only when configured and disclosed, subject to applicable choices.
Is Google advertising active?
This policy does not claim that it is active. It explains the conditions that would apply if Google or other third-party advertisers are enabled, and the policy should be updated with the actual configuration.
How can I remove a downloaded result?
Delete it using your device or browser download controls. Because the current service does not store an account copy, there is no server gallery to clear.