Invert image colors for an email attachment by replacing each decoded RGB channel with 255 minus its value, preserving alpha, and downloading the result as a still PNG.
This creates a negative-style image for a recipient who needs the colors reversed. The Invert Image Colors tool processes PNG, JPEG, GIF, and WebP files in your current browser tab; it does not upload the source to Lizely or send it to an external service. Because the result is always a PNG, check its dimensions and byte size before attaching it.

How to invert an image for an email attachment
- Choose the source file. Select a PNG, JPEG, GIF, or WebP from your device. Its reported size must be 15 MiB or less. The tool checks the actual file bytes instead of trusting the filename extension, file-picker filter, or operating-system MIME label.
- Wait for validation and browser decoding. Allow container detection, decoding, and dimension validation to finish. Truncated files, renamed arbitrary files, and unsupported formats fail before pixel processing. If the decoded dimensions exceed the limits, choose another source rather than expecting the image to be resized automatically.
- Run the inversion and compare the previews. Review the source and complete natural-size PNG previews. Confirm that you selected the intended image and that the reversed colors match the effect you want to send.
- Confirm the dimensions and output byte size. Check the values shown with the result. Nothing is silently resized, cropped, sampled, or partially processed. The complete PNG must also be no larger than 32 MiB; an oversized or failed export does not produce a downloadable result.
- Download the still PNG. Save the generated file. It remains at the source's natural pixel dimensions, even when the original was JPEG, GIF, or WebP. An animated GIF or animated WebP is reduced to its browser-decoded initial frame.
- Attach the downloaded file to the email. In your email compose window, use the service's Attach file or paperclip control, select the downloaded PNG, and wait for the attachment upload to finish. Use the downloaded PNG as-is instead of renaming it with a different image extension.
- Check the size limit before sending. Confirm that the output fits the email service's attachment limit and any recipient restrictions. If it is too large, repeat the process with a smaller eligible source and check the new output, or send the original when inversion is not essential.
What the color inversion changes
The transformation follows a deterministic byte rule: output red equals 255 minus input red, output green equals 255 minus input green, and output blue equals 255 minus input blue. Black becomes white, white becomes black, red becomes cyan, green becomes magenta, and blue becomes yellow. The result therefore looks like a photographic negative, but it is not a lighting, exposure, or tonal-grading correction.
Alpha is copied unchanged, so a semi-transparent pixel remains at the same transparency level. Every decoded RGB slot is processed even when its alpha is zero. However, fully transparent color is invisible, and a browser decoder or Canvas may normalize hidden RGB values before the tool receives them. The tool cannot recover source-file channel data that never reaches the decoded pixel matrix.
File checks that decide whether the PNG can be created
The input must be a complete, supported image container that also passes real browser decoding. Merely having the right filename is insufficient. The checks below determine whether processing can finish and produce a downloadable attachment.
| Check | Allowed value | Practical effect |
|---|---|---|
| Source format | PNG, JPEG, GIF, or WebP only | SVG, AVIF, HEIC, BMP, TIFF, PDF, and other formats are outside scope even if renamed. |
| Input file size | 15 MiB maximum | Both the reported size and the actual ArrayBuffer length are checked. |
| Decoded edge length | 8,192 pixels maximum per edge | A decoded image one pixel beyond the limit is rejected. |
| Decoded pixel area | 24,000,000 pixels maximum | This separate limit catches images that expand into very large pixel buffers after decoding. |
| Output geometry | Complete natural-size PNG | No resizing, cropping, sampling, or partial processing is performed. |
| Output file size | 32 MiB maximum | A null or oversized PNG export fails before a download URL is published. |
Exact boundary values are accepted; one byte, edge pixel, or unit of pixel area beyond a limit causes rejection. Structural detection also does not replace browser decoding. For example, a WebP must have an exact RIFF byte count, the WEBP marker, and a bounded VP8, VP8L, or VP8X first chunk, matching the WebP RIFF container format.
The input and output budgets are separate because a PNG can be much larger than its JPEG, GIF, or WebP source, particularly for photographs or visually noisy images. A valid source below 15 MiB can therefore produce a PNG that exceeds the 32 MiB output limit. In that case, no oversized download is offered.
What the email attachment keeps—and what it loses
The downloaded attachment retains the decoded pixel dimensions and alpha channel, but PNG export creates a new file rather than preserving every property of the source.
- Animation: Animated GIF and animated WebP inputs use the browser-decoded initial frame. Later frames, timing, loops, palettes, and disposal behavior are not preserved.
- Metadata: Canvas export does not promise to retain EXIF, GPS, comments, ICC profiles, provenance, or other source metadata.
- Color management: The tool performs a byte-channel effect rather than a color-managed conversion. It does not linearize gamma, model perceptual complementary colors, remove an orange mask, balance scanned film, correct exposure, or apply tonal grading.
- Source format: JPEG, GIF, and WebP sources become PNG files. The original container is not retained in the output.
Keep the original file whenever animation, embedded profiles, metadata, or exact source encoding matters. Sending the original can also be preferable when the goal is simply to share the photograph rather than demonstrate an inverted or negative-style version.
Review the attachment before sending
A quick final check helps prevent an email with an unwanted visual result or an oversized attachment.
- Open the downloaded PNG and compare it with the preview shown by the tool.
- Confirm that the width, height, visible colors, and transparency are acceptable.
- Check the output's actual byte size against the email provider's limit before composing the message.
- Use a descriptive filename such as inverted-image.png so the recipient can recognize the file.
- If the service rejects the attachment, do not rename or truncate it. Generate a smaller eligible result or attach the original instead.
Local processing improves privacy, but successful decoding does not prove that a file is safe, authentic, or truthful. The tool does not perform malware analysis, content moderation, or authorship verification, so review the attachment before sending it.
Where the image is processed
File reading, format detection, browser decoding, pixel access, inversion, preview generation, and PNG export all happen inside the current browser tab. The source image is not uploaded to Lizely or transmitted to an external processing service.
The final export uses the browser's HTMLCanvasElement.toBlob process. The canvas first encodes the complete natural-size image, after which the tool checks that the resulting PNG exists and fits the output budget before exposing it for download. This local workflow reduces transfer and privacy concerns, while the original file should still be retained whenever its additional properties matter.
Related reading: Overlay Images for Email Attachment: A Local Workflow.
Related reading: Solid Color Image Generator for Instagram: Exact Sizes.