DEV Community: Magill Anway

Resize Images Before You Upload: A Local Checklist for Faster Pages and Fewer Leaks

Magill Anway — Fri, 18 Sep 2026 02:03:30 +0000

Answer first: If you are about to drop a phone photo or a 4K screenshot into WordPress, Drive, or a ticket system, resize (and lightly compress) in your browser on your machine first. Cloud optimizers are convenient — and they are also a third party that briefly holds the exact pixels you care about. Below is a practical checklist plus a local workflow.

Why this keeps showing up

Indie builders keep shipping the same pattern: Canvas / WASM tools that refuse to upload. Roundups of “compress before upload” and WordPress Media Library horror stories circulate every few months. The useful takeaway is not another brand name — it is a habit: treat the image as sensitive until it is the right size, then send it once, to the destination you chose.

Pre-upload checklist (2 minutes)

Know the destination size. Featured image, OG card, avatar, product tile — pick a max width before you open any tool.
Prefer local resize over “upload then hope the plugin fixes it.” Fewer hops means fewer copies and fewer upload-limit failures.
Watch the Network tab. Open DevTools → Network, clear the log, process a non-sensitive test image. Pass = no multipart POST carrying your photo to a third-party API.
Airplane-mode sanity check. After page assets load, go offline and retry. If resize still works, upload-to-server architecture is off the table for that action.
Name the output clearly. hero-1200w-2026-09-18.jpg beats IMG_4832.jpg when you attach it later.

A local resize workflow

Step 1 Cap the long edge

Most blog heroes do not need 4000px. Cap to 1200–1600px on the long edge unless print quality matters.

Step 2 — Resize in the tab

Change dimensions locally. Closing the tab should clear in-memory copies; the downloaded file is the artifact you keep.

Step 3 — Optional light compress

If the file is still huge, compress lightly after resize — still local — then upload once to Media Library / Drive / the real destination.

Step 4 Send once

Skip the detour through a random “free online compressor” host for photos you would not email to a stranger.

One browser-local starting point

When you need an on-device resizer without creating an account, this Image Resizer runs in the tab (files stay on your device):

https://www.lizecheng.net/image/image-resizer/?utm_source=devto&utm_medium=article&utm_campaign=lizely_daily_20260918&utm_content=image-resizer

(That is the only product link in this post.)

What “good enough” looks like

Scenario	Local move
Phone photo → blog hero	Resize to ~1200w → upload once
4K screenshot → ticket	Cap long edge → optional compress → attach
Hit `upload_max_filesize`	Resize first; do not fight PHP limits with a cloud hop
Sensitive ID / face photos	Never use a cloud compressor “just this once

Closing

Image resize is a solved UX problem. The open question is whether the bytes leave your device on the way. Prefer tools you can verify with Network + offline checks — and keep cloud converters for files you would not mind a stranger viewing.

Merge PDFs Locally Before You Share: A Privacy Checklist for Contracts and Scans

Magill Anway — Thu, 17 Sep 2026 02:05:22 +0000

Answer first: If you are combining a signed agreement, ID scans, or medical pages into one PDF, do the merge in your browser on your machine before the file ever touches email, Drive, or a random “free online merger.” Cloud converters are convenient — and they are also a third party that briefly (or longer) holds the exact bytes you care about. Below is a practical checklist plus a local workflow.

Why this keeps showing up

Indie builders keep shipping the same pattern: pdf-lib / WASM tools that refuse to upload. Roundups of “merge PDF with no signup” circulate again every few months. The useful takeaway is not another brand name — it is a habit: treat the packet as sensitive until it is assembled, then send it once, to the destination you chose.

Pre-merge checklist (2 minutes)

Know what is in the stack. Cover sheets, contracts, IDs — remove pages you do not need before merging when possible.
Prefer local merge over “email me the parts.” Fewer hops means fewer copies.\n3. Watch the Network tab. Open DevTools → Network, clear the log, merge a non-sensitive test PDF. Pass = no multipart POST carrying your document to a third-party API.
Airplane-mode sanity check. After page assets load, go offline and retry. If merge still works, upload-to-server architecture is off the table for that action.
Name the output clearly. client-packet-2026-09-17.pdf\ beats merged.pdf\ when you attach it later.

A local merge workflow

Step 1 — Order the sources

Drop files in the order the recipient expects (cover → agreement → appendixices). Reordering after a cloud merge often means another upload.

Step 2 — Merge in the tab

Combine locally. Closing the tab should clear in-memory copies; the downloaded file is the artifact you keep.

Step 3 — Send once

Attach or upload the finished packet to the real destination only. Skip the detour through a random merger host.

Optional — Split first

If you only need pages 2–5 of a larger scan, split locally first, then merge the thin slices. Same rule: Network tab quiet while you process.

One browser-local starting point

When you need an on-device merge without creating an account, this Merge PDF tool runs in the tab (files stay on your device):
https://www.lizecheng.net/pdf/merge-pdf/?utm_source=devto&utm_medium=article&utm_campaign=lizely_daily_20260917&utm_content=merge-pdf

(That is the only product link in this post.)

What “good enough” looks like

Scenario	Local move
2–5 scans for a form	Merge in-tab → upload once
Contract + appendixices	Order carefully → merge → email
Need only a page range	Split locally → then merge thin set
Sensitive IDs	Never use a cloud converter “just this once”

Closing

Merging PDFs is a solved UX problem. The open question is whether the bytes leave your device on the way. Prefer tools you can verify with Network + offline checks — and keep cloud converters for files you would not mind a stranger reading.

Image Resize Before You Upload: A Privacy-First Checklist for Forms, Email, and Social

Magill Anway — Wed, 16 Sep 2026 02:35:06 +0000

Image Resize Before You Upload: A Privacy-First Checklist for Forms, Email, and Social

Answer first: Most “upload your photo” flows (job portals, insurance claims, school forms, Discord/Slack avatars) quietly accept multi‑megabyte originals. That wastes bandwidth, triggers server-side recompression you do not control, and — if you used a random online compressor first — may mean a third party already saw the picture. Resize and compress in the browser on your machine before the upload step. Below is a practical checklist plus a local workflow that never needs a cloud converter.

Why this is hot right now

Indie and open-source circles keep shipping the same pattern for PDFs and images: Canvas / WASM tools that refuse to upload. Roundups of “unlimited free compressors with no signup” are circulating again, and the useful takeaway is not another SaaS name it is a habit: treat the file as sensitive until it is sized for the destination, then upload once, to the destination you chose.

The pre-upload checklist (2 minutes)

Know the destination limit. Avatar 500×500? Application form “max 2 MB? Email attachment 10 MB? Write the number down.
Prefer resize, then compress. Shrinking dimensions usually beats quality-only compression for phone photos.
Strip EXIF when it matters. Location and device metadata hitchhike on JPGs; many local tools let you re-encode without it.
Audit the helper tool. Open DevTools → Network, clear the log, process a non-sensitive test image. Pass = no multipart POST carrying your pixels to a third-party API.
Airplane-mode sanity check. After the page assets load, go offline and retry. If resize still works, upload-to-server architecture is off the table for that action.

A local resize → compress workflow

Step 1 — Hit the pixel budget

If a portal wants 1200px on the long edge, do that first. Exact-dimension resize avoids “still too big” loops after quality tweaks.

Step 2 — Hit the byte budget

Only after dimensions are right, dial quality (or target KB) until the file is under the form limit. WebP when the destination accepts it; JPG when it does not.

Step 3 — Upload once, to the real destination

Skip the detour through a random “free compressor” host. Your browser can do the heavy lifting; the only server that should receive the final bytes is the form you are submitting.

Optional — PDF packets of scans

If the next step is “merge three resized scans into one PDF,” keep that merge local too. Same rule: Network tab quiet while the file is processed.

One browser-local starting point

When you need an on-device resize without creating an account, this Image Resizer runs in the tab (files stay on your device):

https://www.lizecheng.net/image/image-resizer/?utm_source=devto&utm_medium=article&utm_campaign=lizely_daily_20260916&utm_content=image-resizer

(That is the only product link in this post.)

What “good enough” looks like

Destination	Typical target	Local move
Avatar / profile	≤ 512–1024 px	Exact resize + mild compress
Job / visa forms	Often ≤ 1–2 MB	Resize long edge → compress to KB
Email	≤ 5–10 MB total	Batch resize before attach
Social feed	Platform-dependent	Prefer WebP/JPG under 1 MB

Closing

Cloud converters are convenient until the photo is a passport scan, a child’s face, or a whiteboard with customer data. Build the habit: resize locally, verify the Network tab, upload once. The tooling is already in your browser — you do not need another account to use it.

Stop Uploading Sensitive PDFs: A 5-Minute Network-Tab Audit + Local Browser Workflow

Magill Anway — Tue, 15 Sep 2026 06:48:26 +0000

Answer first: Before you drop a contract, payslip, or ID scan into any "free online PDF tool," open DevTools → Network, clear the log, then run the tool. If you see a multipart upload or a request to api.*.com carrying your file bytes, that document already left your machine — privacy policy wording does not undo that. Prefer tools that process files in the tab (Canvas / pdf-lib / WASM). Below is a repeatable audit plus a private compress → merge workflow you can finish in under five minutes.

Why this is hot right now

Over the past week, DEV and GitHub have been full of the same pattern: privacy-first PDF/image suites that refuse to upload (browser-only WASM/JS tools, CSP connect-src 'self' experiments, “verify with Network tab” posts). The shared pitch is simple — cloud converters are convenient until the file is regulated or embarrassing. The useful takeaway for working developers is not “another SaaS exists,” but a habit: treat every online converter as untrusted until the Network panel says otherwise.

The 5-minute Network-tab audit

Open Chrome/Firefox/Edge DevTools (F12 or Cmd+Opt+I).
Go to the Network tab. Check Preserve log. Click the clear (🚫) button.
Optionally filter by Fetch/XHR (or disable cache and leave “All” on).
Pick a non-sensitive test PDF or JPG (a blank page is fine).
Run the online tool’s compress / merge / convert action.
Watch for:
- POST / PUT with a large payload right after file pick
- Hosts like api*, upload*, CDN buckets, analytics SDKs firing on drop
- A progress bar that only moves while a request is in flight

Pass criteria: while the file is being processed, you should see no request that carries the document body. Asset loads for the app itself (JS, WASM, workers) are normal. File bytes going to a third-party origin are not.

Extra check: after the page has loaded once, flip to airplane mode and try again. If the tool still works offline, upload-to-server architecture is off the table for that action.

A private compress → merge workflow (local browser)

Here is a practical path when you need to ship a smaller, single PDF of scans or screenshots without handing them to a random host.

Step 1 — Shrink heavy photos first

Phone photos and scans are often 3–8 MB each. Compress them locally before they become PDF pages.

Use a browser-local image compressor (e.g. Lizely Image Compressor) in your browser:

Drop JPG/PNG/WebP files onto the page.
Drag the quality slider (start around 60–80% for photos).
Use the split preview to confirm text and edges still look sharp.
Download the compressed copies.

Tip: WebP often wins 20–30% over JPEG at similar visual quality when the destination is the web. Stick with JPEG when the next system only accepts .jpg.

Step 2 — Combine documents without an upload

When you have several PDFs (or several exports) that should be one attachment:

Open Merge PDF:

Browse or drag two or more PDFs.
Reorder with the up/down controls so the page sequence matches what the recipient expects.
Download the merged file.

Merging happens with client-side page copy (lossless concatenation of page objects) — text stays selectable and vectors stay crisp. Password-protected inputs need unlocking first; the tool will skip locked files rather than guess.

Step 3 — Optional: shrink an image-heavy PDF

If the result is still too large for email or a portal cap, try a bounded local pass with a browser-local PDF compressor. It re-encodes eligible embedded JPGs in-browser (with honest limits). Keep the original and spot-check pages before you send anything.

What “local” actually buys you

Concern	Cloud converter	In-browser tool
File leaves device	Yes (by design)	No (bytes stay in tab memory)
Queue / file-size gate	Common	Bound by your RAM, not a free tier
Offline after first load	Rare	Often yes
Auditability	Privacy policy prose	Network tab + airplane mode

None of this replaces good judgment (malware-laden PDFs are still PDFs). It does remove an unnecessary third party from everyday compress/merge chores.

Soft wrap-up

Make the Network-tab check a reflex. Once you trust a tool’s architecture, a local compress → merge loop covers most “please send one smaller PDF” requests without uploading sensitive material.

Lizely’s browser tools (image compress, merge PDF, and friends) run on-device with no signup — useful when you want the workflow above without installing desktop software.

Simple JSON Debugging Habits That Save Time

Magill Anway — Mon, 07 Sep 2026 02:47:22 +0000

When a JSON error appears deep inside an API client, the fastest fix is usually a consistent inspection routine rather than a larger parser.

First, save the raw response exactly as received. Then format it so nesting and delimiters are visible. Check the first character to confirm whether you received an object, an array, a string, or an HTML error page disguised as a 200 response.

Next, validate the contract: required keys, value types, and whether null is allowed. Search for duplicate keys and unexpected arrays, especially when the payload was assembled from several services. If the response can contain user text, remember that escaped quotes and newline characters are valid JSON even when they look unusual.

For debugging logs, keep a readable copy and redact tokens, cookies, and personal data before sharing. Minify only when sending a final payload where bandwidth matters. A short checklist like this turns most “unexpected token” messages into a precise location and an actionable fix.

A browser-based formatter can help inspect a sample quickly:
https://www.lizecheng.net/dev/json-formatter/?utm_source=dev.to&utm_medium=forum&utm_campaign=lizely_daily_20260907&utm_content=json-formatter