Why I Built Another Image Converter

Image conversion sounds like a solved problem—until someone sends you a HEIC photo, a website rejects your PNG, or a client needs 40 images resized and converted before a deadline.

Desktop applications can handle these tasks, but installing a full editor just to change a file format feels excessive. Command-line tools are powerful, but they are not accessible to everyone.

That is the problem I wanted JPG.now to solve.

JPG.now is a browser-based image toolkit for converting, compressing, resizing, and inspecting images. It supports JPG, PNG, WebP, AVIF, HEIC, RAW camera files, PDFs, office documents, and more than 90 other formats.

No software installation is required, and the core conversion tools can be used without creating an account.

More Than a JPG Converter

The name starts with JPG, but the project has grown into a broader image-processing toolkit.

You can use it to:

• Convert JPG to PNG, WebP, AVIF, PDF, GIF, TIFF, ICO, and other formats
• Convert HEIC, PNG, WebP, PSD, TIFF, SVG, and other images to JPG
• Develop RAW camera formats such as CR2, CR3, NEF, ARW, RAF, DNG, and RW2
• Convert PDFs and office documents into images
• Compress JPG and PNG files
• Resize images and remove metadata
• Combine multiple images into a PDF
• Process several files in one batch

There are also AI-powered image tools, including:

• Background removal
• 2× and 4× image upscaling
• OCR for extracting text from images
• Text-to-image generation
• A browser-based photo editor

The goal is to cover the small but frustrating image tasks that appear during everyday development, design, content creation, and office work.

Designing the Conversion Workflow

One challenge with conversion websites is that they often make a simple job feel complicated.

JPG.now uses a source-and-target workflow:

1. Select the format you currently have.
2. Choose the format you want.
3. Add one or more files.
4. Adjust options such as quality, dimensions, or metadata.
5. Convert and download the results.

The homepage starts with JPG as the input, but users can switch to another source format or search the full format list.

Options appear as part of the same workflow. A user converting a JPG can set output quality, enter new dimensions, and decide whether to remove EXIF metadata without visiting several different tools.

This matters because conversion, compression, and resizing are related, but they are not the same operation:

• Conversion changes the file format.
• Compression reduces the amount of data in the file.
• Resizing changes the pixel dimensions.

Keeping these controls separate gives users more predictable results.

Handling Real-World File Formats

Supporting a few common formats is relatively easy. Supporting files from cameras, phones, design software, and office applications is where things get interesting.

Real uploads may contain:

• EXIF orientation that must be applied before conversion
• Transparent pixels that JPG cannot represent
• Embedded color profiles
• Multiple pages or frames
• Very large image dimensions
• Camera-specific RAW data
• Incorrect or misleading file extensions

For example, converting a transparent PNG to JPG requires choosing a background because JPG does not have an alpha channel. JPG.now flattens transparent regions onto a solid background instead of producing unexpected black areas.

Camera photos also need orientation correction. A photo may appear upright in a phone gallery while its stored pixels are rotated, with EXIF metadata telling the viewer how to display it. If that metadata is removed before applying the orientation, the converted image may come out sideways.

These details are mostly invisible when everything works—which is exactly how a conversion tool should feel.

Browser-Side vs. Server-Side Processing

JPG.now uses a hybrid processing model.

Lightweight utilities can run directly in the browser. This works well for calculations or inspections that do not need expensive processing, including:

• Aspect-ratio calculations
• DPI and print-size calculations
• Image format comparisons
• Metadata inspection
• File-size estimates

Heavier operations are processed by server-side workers. These include complex conversions, RAW development, OCR, and AI image processing.

This split provides two useful properties:

• Small utilities respond immediately and can keep data on the device.
• Resource-intensive jobs can use the libraries and compute capacity they need without requiring users to install anything.

Conversions are also processed independently, allowing batch uploads to run in parallel instead of forcing every file through one long sequential queue.

Privacy Had to Be Visible

Uploading an image to a website creates an obvious question: what happens to the file?

JPG.now uses HTTPS for uploads and automatically removes guest files within 24 hours. According to the site’s privacy information, uploaded content is not indexed, shared, sold, or used to train AI models.

Tools that run entirely in the browser do not need to upload the image at all.

The interface surfaces file-retention information near the upload workflow because privacy should not be hidden several pages deep in legal text.

For especially sensitive material, local desktop or command-line processing is still the safest option. An online converter should be convenient, but it should also be honest about when a file leaves the user’s device.

Useful Tools for Developers and Designers

Some of my favorite parts of the project are the smaller utilities around conversion.

The free image tools include:

• An aspect-ratio calculator
• A DPI/PPI and print-size calculator
• An image file-size estimator
• An EXIF metadata viewer
• A dominant-color palette extractor
• A JPG, PNG, and WebP comparison tool
• A social-media image-size reference

These are simple utilities, but they solve questions developers repeatedly encounter:

• What height preserves the original ratio at 1,200 pixels wide?
• How large will this image print at 300 DPI?
• Is WebP actually smaller for this particular asset?
• Does this photo contain GPS metadata?
• Which colors should I extract for the surrounding interface?

Instead of answering those questions with guesswork, the tools make the relevant information visible.

Free Access Without Requiring Registration

The guest tier currently supports up to 10 conversions per day and files up to 10 MB without an account. A free account increases those limits to 20 daily conversions and 50 MB per file.

Optional Premium plans are available for larger uploads, unlimited conversions, longer history, API access, and higher-volume workflows.

I wanted the basic experience to remain useful before asking someone to register. A visitor with one incompatible image should be able to solve the problem and leave.

What I Learned

Building JPG.now reinforced a few ideas that apply to many developer tools.

Simple tools still have difficult edge cases

The interface may say “convert,” but the implementation must deal with color modes, transparency, orientation, malformed files, memory limits, multi-page documents, and format-specific behavior.

Defaults are part of the product

Most users do not know which JPG quality level or resize algorithm they need. Sensible defaults matter, while advanced controls should remain available for people who understand the trade-offs.

Privacy needs product design, not just a policy

Retention periods, upload behavior, and client-side processing should be explained where the user makes the decision to upload.

Good utilities explain the underlying concepts

A useful converter should help people understand why PNG works better for screenshots, why JPG works well for photographs, and when WebP or AVIF is the better delivery format.

Try It

You can try the converter at jpg.now or browse the complete image-tool directory.

I would especially appreciate feedback from developers, photographers, and designers:

• Which formats are still painful in your workflow?
• Which conversion options do you regularly need?
• Would an image-conversion API be useful in your projects?
• What would make the batch workflow better?

JPG.now began with a narrow goal: make JPG conversion quick and uncomplicated. It is gradually becoming a practical image toolbox for all the awkward files that show up in real-world work.