DEV Community: SAHU Khan

How to Convert JPG Images to PDF Without Installing Anything (Free)

SAHU Khan — Sat, 17 Oct 2026 03:39:10 +0000

Scanned documents, assignment submissions, ID proofs, invoices — so much of everyday paperwork ends up as a pile of JPG photos that really should be a single PDF. Most people fire up a desktop app or upload sensitive files to some random converter site. There is a simpler way: convert your images to PDF right in the browser, for free, with no sign-up.

Why JPG to PDF still matters

PDFs are the universal format for documents. They keep page order, print cleanly, and open identically on every device. A set of JPG photos, on the other hand, is hard to email as one package and awkward to print. Converting images to a single PDF takes seconds and solves both problems.

The step-by-step process

Open the JPG to PDF Converter on Napizo.
Drag and drop your JPG images into the tool, or click to browse and select them.
Arrange the images in the order you want them to appear as pages.
Click convert, then download your merged PDF.

That is genuinely all there is to it. The conversion happens locally in your browser — your images are never uploaded to a server, which is exactly what you want when the files contain personal documents.

Practical tips

Scan order matters. If you photographed a multi-page form, double-check the page order before converting. Renaming files 01, 02, 03 beforehand helps.
Watch the file size. Phone photos can be huge. If the resulting PDF is too big to email, run the images through an image compressor first, or keep the PDF under your email provider's attachment limit.
One image per page vs. collage. Most converters place one image per page, which is ideal for documents. For photo albums, you may prefer a collage layout — plan accordingly.
Keep originals. Always archive the original JPGs before converting, in case you need to re-edit or re-crop later.

When this beats the alternatives

Operating systems have built-in "print to PDF" tricks, but they are clunky for multiple images: on Windows you select images, right-click, print, and choose Microsoft Print to PDF; on macOS you open Preview and export. Both work, but a dedicated browser tool is faster, works the same on every OS, and needs nothing installed — handy on a borrowed or locked-down computer.

The bottom line: if you regularly turn photos into documents, bookmark a free converter and skip the software hunt. The JPG to PDF Converter handles the job in under a minute, and Napizo's full set of free browser tools covers the rest of your image and document chores.

I merged 10 scanned pages into one PDF in 30 seconds

SAHU Khan — Mon, 12 Oct 2026 07:12:19 +0000

Last week I scanned a 10-page document with my phone — and ended up with 10 separate image files. Emailing 10 attachments is messy, and the recipient has to open each one. Here's the 30-second fix.

The problem with separate files: Multiple attachments get opened out of order, one always goes missing, and on mobile it's a nightmare. One combined PDF just works — page 1 to 10, in order, single download.

The workflow:

Open the PDF merger at https://napizotools.com/pdf-merger
Upload your files in the order you want them (JPG scans work too — the tool converts and merges).
Drag to reorder if needed, then click merge.
Download the single combined PDF.

That's it. My 10 phone scans became one tidy 2 MB PDF in about half a minute.

Two things worth knowing: First, check the page order before downloading — a contract with page 3 before page 2 is worse than separate files. The 5-second reorder check is the whole quality step. Second, the merge runs entirely in your browser — your scans are never uploaded anywhere, which matters for ID documents and contracts.

Use cases beyond scans: job applications (resume + cover letter + certificates as one file), monthly receipts as a single PDF, combining report chapters from different authors.

How I shrunk a 12 MB PDF to 1 MB without losing quality

SAHU Khan — Mon, 12 Oct 2026 06:51:22 +0000

Last week I needed to email a scanned 12 MB PDF and the mail server bounced it. No fancy software on hand, no time to install anything. Here's the 2-minute workflow that got it down to about 1 MB with no visible quality loss.

Why PDFs get so bloated

Scanned PDFs are the worst offenders — every page is a full-resolution image, often 300 DPI or more. A 10-page scan can easily hit 30–50 MB.

The workflow

Open the PDF compressor at https://napizotools.com/pdf-compressor/ — it runs entirely in your browser.
Drop in your PDF (drag and drop, or tap to browse).
Pick a compression level. Start with the balanced/default setting.
Hit compress, then download the result.

My 12 MB scan came out at roughly 1.1 MB. Text was still crisp, signatures legible, and it sailed through email.

Why quality survives

PDF compression re-encodes embedded images at sensible resolutions and strips redundant data. Most bloat is resolution far beyond what any screen or home printer can show — removing that costs you nothing visually.

When to push harder (and when not to)

Email/WhatsApp sharing — aggressive compression is fine.
Forms and official documents — use light compression.
Print-ready files — don't compress at all.

One gotcha: after compressing, zoom to 200% on one text-heavy page and one image-heavy page. If both look clean, you're done.

The whole thing runs client-side, so a 12 MB file never leaves your machine — which, for contracts and ID scans, matters more than the compression itself.

How a Background Remover Can Run 100% in Your Browser

SAHU Khan — Sun, 11 Oct 2026 06:54:31 +0000

A few years ago, removing a photo's background meant uploading it to some server, waiting in a queue, and hoping the service didn't keep a copy. Today you can open a web page, drop in a photo, and get a clean cutout in seconds — with your file never leaving your device. Here's how that works under the hood.

It starts with a segmentation model

Background removal is an image segmentation problem: for every pixel, the model decides "foreground" or "background". Researchers trained convolutional neural networks on thousands of labeled portraits and product shots until they got very good at finding edges — hair, fur, transparent glass, the hard cases.

The trick that brought this to the browser was making those models small and portable. Models are exported to formats like ONNX, quantized down, and compiled to run on WebAssembly or WebGPU. What used to need a GPU server now runs on your laptop's CPU or integrated graphics in a couple of seconds.

What actually happens when you drop in a photo

Decode locally. The browser reads your image with the Canvas API or createImageBitmap — no upload involved.
Run inference. The quantized model processes the image tensor right in the page (often via onnxruntime-web), producing an alpha mask.
Refine the mask. A bit of feathering/edge smoothing cleans up halos around hair.
Composite and export. The foreground is drawn onto a transparent canvas and exported as PNG — all client-side.

Why "in the browser" is a bigger deal than it sounds

Privacy. Personal photos, ID documents, product shots for an unreleased launch — nothing traverses the network.
No queues or accounts. There's no server capacity to ration, so there's nothing to sign up for.
Offline after first load. Once the page and model weights are cached, it can even work with flaky connectivity.

Try it yourself

If you want to see it in action, Napizo's free background remover does exactly this: open the page, drop in a JPG or PNG, and download the transparent PNG. Because the model runs in your browser, there's no upload, no sign-up, and no watermark — your file never leaves your device.

The broader lesson: the browser has quietly become a serious compute platform. When the model fits in a few megabytes of WASM, "AI-powered" stops meaning "send your data to our cloud" — and that's a win for users and developers alike.

I Built 15 Free Browser Tools That Never Touch a Server

SAHU Khan — Fri, 09 Oct 2026 05:35:05 +0000

I Built 15 Free Browser Tools That Never Touch a Server

A few months ago I started building something simple: free online tools that do their entire job inside your browser. Today the collection — Napizo — has 15 tools: PDF to JPG, JPG to PDF, PDF merger, PDF compressor, image compressor, image resizer, background remover, QR code generator, word counter, an AI caption generator, an InPage Urdu-to-Unicode converter, an EPUB splitter, and a few more.

The unusual part isn't the tool list. It's the architecture: your files never leave your device. No uploads, no sign-up, no server processing your documents. Here's what I learned building it that way.

Why client-side was the right call

Most free tool sites work like this: you upload your file, their server processes it, you download the result. That model has real costs — bandwidth, compute, storage — which is exactly why those sites are covered in ads and paywalls.

Running everything in the browser flips the economics: the user's device does the work, so there is no per-file server cost at all. It also kills the biggest trust question for a tools site — "where did my file go?" — because the answer is verifiable: nowhere.

The tech stack is boring (deliberately)

There's no backend framework. The stack is HTML/CSS/JavaScript plus battle-tested client-side libraries: PDF work runs on pdf.js and pdf-lib entirely in memory; image work uses the Canvas API and Web Workers; OCR for the PSD converter uses Tesseract.js rebuilt into layered files via ag-psd.

"Boring" matters here: fewer moving parts means the tools keep working even on a plain static host, and every tool is auditable by anyone who opens dev tools.

The hard parts nobody warns you about

1. Memory on mobile. A phone browser will kill your tab if you load a 100-page PDF into RAM carelessly. The fix: process pages in chunks, release object URLs promptly, and never keep the full decoded document in memory longer than necessary.

2. Trust signals. A free tools site with no company behind it has to earn trust differently: clear privacy copy ("files stay in your browser"), an honest limitations page, and About/Contact/Privacy/Terms pages that read like a real site. We published all of them before caring about SEO at all.

3. Saying what tools CAN'T do. The PSD converter's "editable text layers" are AI-reconstructed via OCR — fonts won't match the original. We say that on the tool page itself. Short-term it costs conversions; long-term it's the only way people come back.

What I'd tell anyone starting this

Ship the tool that solves one person's Tuesday-morning problem — compressing a PDF for an email attachment, resizing a photo for a form upload. Boring problems, done instantly, with zero friction. Then make the privacy story the headline, not a footnote.

The full collection is live here if you want to try the tools: https://napizo.netlify.app