Novus Convert
Compress JPG, PNG & WebP without changing the format
Use the separate /compress surface in Novus Convert to re-encode a JPG, PNG, or WebP at a quality level you choose, shrinking the file locally while keeping its format, and confirm the measured result size before you download.
Sometimes a file is already the right format and simply too heavy. A JPG that is fine for the web but too large for an email, a PNG screenshot that bloats a page, a WebP that could be leaner — none of those need a new format, they need to weigh less. That is a different job from conversion, and Novus Convert gives it a different home: the compression surface at convert.novusstreamsolutions.com/compress, which is deliberately kept separate from the converter at /convert.
Compression changes the size of a file, not its format. A JPG stays a JPG, a PNG stays a PNG, a WebP stays a WebP — the app re-encodes the image at a quality level you set, runs the whole thing locally in browser memory, and shows you the measured result size before you download anything. This guide covers when to reach for /compress instead of /convert, how to read the before-and-after numbers, how to pick a quality level by looking at the actual image, and how to stack a conversion and a compression when a file needs both.
Contents
- 1.1. Compression changes the size, conversion changes the format
- 2.2. Open /compress, a deliberately separate surface
- 3.3. Load a JPG, PNG, or WebP and read the starting size
- 4.4. Choose a quality level by looking at the file
- 5.5. Read the measured result before you download
- 6.6. Stack a conversion first, then compress
Two ways to finish
Same format, smaller file
You already have a JPG, PNG, or WebP and just need it lighter — drop it into /compress, set a quality level, and read the measured result.
Convert first, then compress
A file needs a new format and a smaller size, so change the format at /convert, then take that output to /compress and shrink it.
- 1
1. Compression changes the size, conversion changes the format
These are two separate operations, and choosing the right one saves you from fighting the wrong tool. Conversion, at /convert, turns one format into another — a HEIC into a JPG, a PNG into a WebP. Compression, at /compress, leaves the format exactly where it is and makes the file smaller by re-encoding it at a lower quality. If the format is already correct and only the size is a problem, you want compression, not conversion.
The practical test is to ask what is actually wrong with the file in front of you. If a strict uploader rejects the format, or a website needs WebP instead of PNG, that is a format problem and it belongs at /convert. If the format is fine and the file is simply too large to attach, upload, or serve quickly, that is a size problem and it belongs at /compress. When both are true, you handle them in order, which the final step covers.
- Same format, smaller file: use /compress.
- Different format: use /convert.
- Need both: convert first, then compress.
- 2
2. Open /compress, a deliberately separate surface
Go to convert.novusstreamsolutions.com/compress. This surface does one thing on purpose, so there is no output-format selector to distract you — the only decision is how hard to compress. It accepts three inputs: JPG, PNG, and WebP. Those are the raster formats where a quality control has a meaningful, adjustable effect, so they are the ones the compression workflow exposes.
Everything happens on your device. The file is re-encoded in browser memory, never sent to a remote service, and Novus Convert identifies each file by its signature rather than its filename, so a mislabeled image is caught before it is processed. If you drop in a format the compressor does not accept, that is a sign the job actually starts at /convert instead.
- 3
3. Load a JPG, PNG, or WebP and read the starting size
Drag a file in or pick it with the file chooser. Before you change anything, note the original size the app reports — this is your baseline, and every decision from here is measured against it. Knowing you are starting from, say, 4.2 MB is what makes the result meaningful; a smaller number means nothing without the number it started from.
Keep the three accepted inputs in mind. If your source is a HEIC from an iPhone, an AVIF, a TIFF, or anything other than JPG, PNG, or WebP, the compressor is not the right first stop — take it to /convert to produce one of the three compressible formats, then come back here. Loading the wrong type is not a failure so much as a nudge toward the correct order of operations.
- 4
4. Choose a quality level by looking at the file
The quality control is the whole point of this surface. Lower quality means a smaller file and more visible compression; higher quality means a larger file that stays closer to the original. There is no single correct setting, because the right level depends on what the image is and where it is going, so let the content of the file guide the number rather than reaching for a habit.
Photographs are forgiving — continuous tone and soft detail hide a lot of compression, so you can push the quality down noticeably before anyone would tell. Flat graphics, screenshots, logos, and anything with text or hard edges are the opposite: artifacts show up early as fuzz and halos around sharp lines, so those want a gentler setting. Because the format never changes, a PNG or WebP with transparency keeps its alpha channel throughout — compression here shrinks the file without flattening a see-through background.
- Photographs tolerate a lower quality before damage shows.
- Text, logos, and sharp edges show artifacts sooner.
- Transparency survives, because the format does not change.
- 5
5. Read the measured result before you download
After compressing, Novus Convert shows you the measured size of the result, not an estimate — the actual bytes of the re-encoded file. Compare it to the baseline you noted in step three to see exactly what the quality level bought you. If the drop is disappointing, or if it is large enough that you suspect visible damage, that is your cue to adjust the quality and re-run rather than accepting the first attempt.
The download button appears only after the result passes validation, so a file you can download is a genuine, decodable image and not just something with the right extension. Structural validity, though, is not the same as looking good — open the compressed file at full size and check the places compression shows first: text edges, skin tones, gradients like skies, and the boundary between a subject and its background. If it looks soft, raise the quality; if it looks perfect and the size still feels heavy, you have room to push lower.
- 6
6. Stack a conversion first, then compress
Conversion and compression are built to work in sequence when a file needs both a new format and a smaller size. A common example is an iPhone photo: convert the HEIC to a JPG at /convert, which decodes locally through a WebAssembly worker so the photo is never uploaded, then bring that JPG to /compress and shrink it until it fits the destination. Each surface does its own job cleanly, and running them in order beats trying to force one tool to do both.
Mind the practical boundaries while you work. Image inputs are accepted up to 100 MB and 80 megapixels, and JPG, PNG, and WebP each draw on a daily download allowance that resets by local calendar day — the remaining count sits beside the download control, so free is not the same as unlimited. Results live behind temporary object URLs that vanish when you remove the job or close the tab, so save each compressed file you want before you leave.
- iPhone photo: HEIC to JPG at /convert, then shrink it at /compress.
- Images are accepted up to 100 MB and 80 megapixels.
- Save downloads before closing — result URLs are temporary.
Compress for the destination, not out of habit
Let the file and its destination pick the quality level instead of applying one setting to everything. Push photographs harder and treat text, logos, and screenshots gently, always compare the measured result against the size you started from, and open the output at full scale before you trust it. When a file needs a new format as well, convert it at /convert first and compress the result here — two clean steps in order, each shown and validated locally before anything downloads.
Frequently asked questions
Quick answers to common questions about this topic.
Does compressing an image change its format?
No. The /compress surface keeps the format exactly as it is — a JPG stays a JPG, a PNG stays a PNG, a WebP stays a WebP. It re-encodes the image at a quality level you choose to make the file smaller. Changing the format is a separate job that lives at /convert.
Where is the compression tool, and why is it not on /convert?
Compression has its own surface at convert.novusstreamsolutions.com/compress, kept deliberately separate from the converter at /convert. The converter changes formats and can run mixed batches; the compressor does one thing, so its only control is the output quality.
Can I compress a PNG or WebP without losing its transparency?
Yes. Because compression does not change the format, a PNG or WebP keeps its alpha channel through the process. The file gets smaller, but the see-through background is preserved rather than flattened onto white.
How do I make an image both a different format and a smaller file?
Run the two operations in order. Convert the file to the format you need at /convert, then take that output to /compress and reduce its size. For example, convert a HEIC to JPG first, then compress the JPG until it fits your destination.