DEV Community: Vikky

How to submit handwritten homework as one readable PDF from your phone

Vikky — Wed, 07 Oct 2026 18:49:29 +0000

Plenty of courses still run on paper. You solve the problem set by hand, and then the learning platform (Google Classroom, Canvas, Moodle, a college portal) asks for "a single PDF". The same few problems tend to come up: pages out of order, sideways photos, pencil that vanished in compression, and a huge file that's slow to open on a laptop. Here's a short workflow that avoids all of them, using nothing but the phone you already have.

1. Write for the camera, not just the page

A few small choices make the photo far easier to read later:

Use a dark pen or a soft pencil (2B or darker). Light HB pencil looks fine on paper and almost disappears once the file is compressed.
Leave a margin. Writing right up to the edge means the edge is what gets cropped.
Number every page at the top, like "Q3 – page 2 of 4". If anything ends up out of order, the reader can still follow it.
Write your name on page one. File names get renamed by portals; the page doesn't.

2. Photograph each page the same way

Consistency matters more than an expensive camera.

Put the sheet on a plain, darker surface so the page edge stands out.
Stand so the light comes from the side. Overhead light puts your phone's shadow right across the middle of the page.
Hold the phone flat and parallel to the paper. Tilted shots turn the page into a trapezoid, and the bottom lines get smaller and blurrier.
Fill the frame with the page but keep all four corners visible.
Skip the flash. On glossy worksheets it creates a white patch exactly where your working is.

Take a second shot of any page you're unsure about. Re-shooting now takes five seconds; re-shooting after the deadline isn't possible.

3. Check orientation before you convert

Phones store rotation as a flag in the photo's metadata, and not every app respects it. A page that looks upright in your gallery can come out sideways in a PDF. Open each photo once, and if it's rotated, use the gallery's rotate button and save. That bakes the rotation into the image itself.

4. Put the pages in order, then make one PDF

Most portals accept one file per assignment, so merge everything into a single document. I use JPG to PDF Mobile, a free converter that runs entirely in the browser: you add the photos, drag them into order, pick a page size and convert. Because the conversion happens on the device, the photos aren't uploaded anywhere, which is nice when a worksheet has your full name and student ID on it. Any converter that lets you reorder pages and choose quality will do; the important part is the order and the settings, not the tool.

Settings that work well for handwritten pages:

Page size: A4 or Letter, whichever your school uses. "Fit to image" is fine too, but a fixed size prints more predictably if the teacher prints submissions.
Quality: start at the balanced/medium setting. Handwriting is high-contrast, so it survives moderate compression much better than photos of people do.
File size target: check the portal's upload limit first; it's usually shown next to the upload button, and some forms are as strict as 1–2 MB. If you're over, drop one quality step and convert again rather than deleting pages.

5. Open the PDF the way your teacher will

Before you upload, open the finished PDF on your phone and zoom in to 100% on the hardest page, usually the one with the smallest writing or the faintest pencil. Ask yourself:

Can I read every line without squinting?
Are the pages in the order I numbered them?
Is anything cut off at the edges?
Is the file under the portal's size limit?

If all four are yes, upload it. If not, fix the specific page and regenerate. It's much faster than redoing everything.

6. Name the file like a grown-up

Portals often keep your original file name, and teachers download dozens of them. Something like Surname_Firstname_Physics_HW3.pdf makes life easier for whoever grades it, and makes it easy for you to find again if there's a dispute about a missing submission.

A two-minute version

If you're in a hurry: dark pen, side light, phone flat, fix rotation, merge in order, medium quality, zoom-check the worst page, sensible file name. That's the whole routine, and it turns "the PDF won't open / page 3 is sideways" emails into a thing of the past.

If you have a trick for getting faint pencil to show up better in photos, I'd love to hear it in the comments.

How to Turn a Pile of Receipt Photos into One Clean PDF on Your Phone

Vikky — Wed, 07 Oct 2026 06:45:39 +0000

Expense claims, warranty returns and rent records all tend to end the same way: someone asks for "the receipts as one PDF". If your receipts live as twelve photos in your camera roll, that one request can eat half an hour. Here is the workflow I've settled on for doing it from a phone, with fewer rejected uploads and less re-shooting.

1. Shoot the receipt so it survives compression

Most claim portals and finance inboxes cap uploads somewhere between 1 and 5 MB, so your PDF will often be compressed. Thermal paper receipts are faint to begin with, and compression is where they turn unreadable. A few habits help a lot:

Flatten it first. Curled receipts throw shadows across the totals. Press it under a book for a minute or tape the corners down.
Use a dark, plain background. White receipt on a dark table gives the camera a clean edge and better exposure.
Light from the side, not above. Overhead light puts your phone's shadow right on the paper.
Fill the frame, then stop. Get close enough that the text is large, but keep all four corners visible. Reviewers want to see the merchant name, the date and the total in one shot.
Turn off the flash. Flash glare on glossy or thermal paper wipes out exactly the line you need.

If a receipt is long (fuel stations and supermarkets love these), take two overlapping photos rather than one tiny one. Two readable pages beat one illegible page.

2. Name and order before you convert

The order of pages in the PDF is the order a reviewer reads them in. Decide it before converting, not after:

Chronological works for trip expenses and monthly records.
Grouped by category (travel, meals, lodging) works when the claim form has separate lines.
Invoice first, then proof of payment works for warranty and refund requests.

Put the summary item first. If the claim form asks for a total, a reviewer who sees the biggest receipt on page one is less likely to bounce it back.

3. Merge the photos into one PDF

You don't need a scanner app with a subscription for this. Any converter that can merge several images and let you reorder them will do. The one thing I check now is where the conversion happens. Receipts carry card digits, addresses and sometimes names, and plenty of free converters upload every image to a server first.

I use jpgtopdf, a free JPG to PDF converter that runs in the browser, so the photos stay on the phone. You add the images from the gallery or the camera, drag them into order, pick a page size and convert. Whatever tool you pick, the steps are similar:

Select all the receipt photos at once.
Drag them into the order you decided above.
Choose A4 (or Letter in the US) if the PDF might be printed, or "fit to image" if it's only going to be read on screen.
Convert, then open the PDF once before sending it.

4. Hit the size limit without wrecking readability

If the merged file is too big, lower the quality one step at a time and re-check the faintest receipt each time. The total and the date on that receipt are your readability test. A few rules of thumb:

Change one setting at a time. Drop quality a notch, convert, check, and only then try the next step down.
Don't shrink the page size to save bytes. It makes text smaller without saving much. Lower the image quality instead.
Split rather than crush. If a portal allows several attachments, two clear PDFs are better than one blurry one.

5. Check before you hit send

Thirty seconds of checking saves a week of back-and-forth:

Every page is upright and in the order you intended.
The merchant, date and amount are readable on every page when you zoom to 100%.
Nothing extra slipped in (a screenshot, a photo of your desk).
The file name says what it is: 2026-10-expenses-travel.pdf beats document(3).pdf.

6. Keep the originals for a while

Thermal receipts fade, sometimes within months. Keep the photos as well as the PDF, at least until the claim is paid or the warranty period ends. A folder per month in your gallery or cloud storage is enough.

That's the whole routine: flatten, shoot on a dark background, order, merge, shrink carefully and check. If you have a trick for faded thermal receipts that I haven't covered, I'd like to hear it in the comments.

Getting Scanned Documents Under Portal Size Limits (On Your Phone)

Vikky — Mon, 05 Oct 2026 10:21:52 +0000

You finally finished scanning your certificates. The portal says “Upload PDF (max 200 KB)”—or 500 KB, 1 MB, 2 MB—and your file is 4.8 MB. Or it accepts the size but rejects the upload because pages are in the wrong order, the file is password-protected, or each photo is a separate attachment when they wanted one merged PDF.

This guide is for that moment. It focuses on phone-first workflows: using what you already have (Camera, Files, Photos) plus a browser converter when you need merge, reorder, page size, and compression without installing a heavy desktop app.

These are the failure modes that show up again and again on admission, scholarship, KYC, and job portals.

What portals usually care about

Most upload rules boil down to a handful of checks:

File type — almost always PDF (sometimes JPG only for a photo field).
Maximum size — commonly somewhere between about 100 KB and 2 MB for document packs; photo fields may be smaller.
Page size / dimensions — A4 is common for multi-page sets; ID slots may want a specific aspect.
Page count and order — e.g. application form first, then ID, then certificates.
No password / no encryption — locked PDFs often fail silently.
Readable text or clear scan — blurry phone photos get human rejection even when size is fine.

If you only shrink the file but ignore order or clarity, you can still get rejected.

Step 1: Capture better before you compress

Compression cannot invent detail that was never in the photo.

Light: Face a window or use even indoor light; avoid harsh flash glare on glossy certificates.
Angle: Shoot straight-on; skewed pages waste pixels on background and look unprofessional.
Fill the frame: Crop clutter in your gallery app before converting.
One page per shot unless the portal explicitly wants a single photo of a spread.
Prefer the document scanner mode in Google Drive, Microsoft Lens, Adobe Scan, or your phone’s built-in scanner if you have it—these flatten perspective better than a casual Camera roll shot.

Save or export as clear JPG/PNG first. You will turn them into PDF next.

Step 2: Decide page size on purpose

Portals that generate printable packets often expect A4 (common outside the US) or Letter. Fitting a tall phone photo onto A4 with huge white margins is fine for readability; stretching a wide panorama into a square page is not.

Rules of thumb:

Multi-page academic / government packs: A4 or Letter, portrait, consistent margins.
Single ID image fields: sometimes the portal wants JPG, not PDF—read the label.
“Fit to image” helps when you only need one photo per page and do not care about standard paper size—but some portals are picky about dimensions, so prefer A4/Letter when unsure.

Tools that let you pick page size before export save a re-upload cycle. In JPG to PDF Mobile you can choose A4, Letter, Legal, or fit-to-image and use ID-oriented presets when you are preparing Aadhaar/PAN/passport-style pages.

Step 3: Merge and order pages before you shrink

Portals that say “upload a single PDF” will reject a ZIP of images or five separate files.

Collect every page as an image.
Sort them in the exact order the instructions list (form → ID → proofs is a common pattern).
Merge into one PDF.
Only then compress.

Reordering after heavy compression is possible but annoying; order first while thumbnails are easy to read. Drag-to-reorder in a mobile browser is usually faster than renaming IMG_0042.jpg by hand.

Step 4: Compress without making it unreadable

Size limits force a trade-off between clarity and kilobytes.

Practical approach:

Downscale megapixel photos. A 12 MP phone image is overkill for a portal that displays a stamp-sized preview. Resizing the long edge to roughly 1500–2000 px often cuts size dramatically before PDF encoding.
Use JPEG quality carefully. Start around a medium quality setting; if the PDF is still over the limit, lower quality slightly or downscale more. If text becomes muddy, undo and try fewer pages per file if the portal allows multiple uploads.
Avoid double-encoding traps. Exporting a PDF, screenshotting it, and re-PDFing again softens text. Convert once from the best originals you have.
Skip fancy filters. Heavy contrast on already-scanned pages can add noise and size.

If the limit is extremely tight (~100–200 KB for several pages), use fewer pages, grayscale, or a second compress pass. Always zoom into small text (dates, seal numbers) before submitting.

Step 5: Common rejection reasons (and fixes)

What you see / what support says	Likely cause	What to try
“File too large”	Over max KB/MB	Downscale → lower JPEG quality → re-export PDF
“Invalid format”	DOC/HEIC/PNG when PDF required	Export real PDF, not a renamed extension
Blank or corrupt on their side	Password-protected or unusual encryption	Re-save without password
“Upload failed” with no message	Network timeout on big file	Compress more; retry on stable Wi‑Fi
Human reject: “not clear”	Blur, glare, cropped edges	Reshoot, then compress less aggressively
“Wrong document”	Page order / missing page	Re-merge in listed order
Accepts PDF but wants photo	Field expects JPG	Upload image to that field only

Also watch filename rules (some portals dislike spaces or non-English characters) and session timeouts on slow mobile networks—generate the PDF offline, then upload on Wi‑Fi.

Phone workflow checklist (print-friendly)

Use this as a pre-flight list:

[ ] Read the portal’s max size, type, and page-order instructions twice.
[ ] Reshoot any page that is blurry or glare-heavy.
[ ] Crop backgrounds in Photos/Gallery.
[ ] Order images exactly as required.
[ ] Merge to one PDF with intentional page size (A4/Letter unless told otherwise).
[ ] Check total size against the limit.
[ ] If over limit: resize images → reduce quality → export again (once).
[ ] Open the PDF and verify every page is upright and readable.
[ ] Confirm the file is not password-protected.
[ ] Upload on stable Wi‑Fi; keep the PDF until you see a success receipt.

When a browser tool helps

Built-in phone “Print → Save as PDF” is enough for a single image. It gets awkward when you need many pages, reordering, consistent A4, and size control in one place—especially on a phone where desktop apps are not installed.

A browser-based converter that runs on-device is useful here: you stay on the phone, keep sensitive IDs off random servers, and can iterate on compression without emailing files to yourself. If you want to convert JPG to PDF on your phone with merge, reorder, page size, and compression controls, that flow matches the checklist above.

For official rules, always trust the portal’s own help text over any blog—including this one. Portal limits change by season (admissions) and by form.

Quick FAQ

Compress or merge first? Merge and order first, then compress (or resize sources and merge once).

Smaller always better? No—under the limit with readable text beats a tiny blurry file.

Portal wants separate files? Skip merging; use the same capture and compression habits per file.

Closing

Portal uploads fail for boring reasons: too many megabytes, wrong container, scrambled page order, or unreadable scans. Fix capture quality first, set page size deliberately, merge in the documented order, then compress just enough to clear the limit. Keep the final PDF until the status page confirms success. When instructions and file size disagree, the instructions win.