Signature Rejected More Than Once? Check These 4 Things

When a signature rejected multiple times exam form message appears after two or three uploads, you are almost always repeating the same technical failure — not fighting a random server glitch.

Key takeaways

• A signature rejected multiple times exam form pattern means the portal keeps reading the same failing properties from your JPG — pixels, KB, format, or content — not that the server is broken.
• Signature uploads fail on exact pixel width and height plus KB range, separate from photo rules; fixing your photograph does not fix a signature rejection.
• Re-uploading the same file under a new name rarely helps; browsers and portals cache failed attachments until you export a genuinely new JPG from source.
• Ink colour, background grey, and missing triple-signature rows are content failures that pass file-size checks but fail manual or automated review.
• Measuring width, height, and KB on disk before each attempt breaks the retry loop faster than changing browsers or waiting overnight.
• Different exam boards publish different signature pixel boxes — SSC, IBPS, and UPSC are not interchangeable even when all say "signature upload."

Exam portals show minimal error text for signature fields. "Invalid signature," "signature not accepted," or a silent form reset after upload feel opaque when you have already tried twice. The instinct is to tweak random settings — lower quality, switch from scan to photo, change ink — without knowing which gate failed. That scatter approach keeps a signature rejected multiple times exam form cycle alive for days.

This guide treats repeated rejection as a diagnostic problem, not bad luck. You will confirm what the portal actually validates, route to Cause 1 or Cause 2, fix once from source, and stop re-uploading unchanged files. If your photograph was also rejected, handle photo and signature as independent files — mixing fixes between them is a common reason signatures keep failing while photos pass.

Start here: confirm what actually failed

Before editing, open Properties on the exact signature JPG you attached — not a thumbnail, not a preview inside an editing app. Record width in pixels, height in pixels, file size in KB, and format. Compare against the notification for your specific exam cycle.

Write down three numbers before you touch an editor: pixel width, pixel height, and KB. Keep the official notification open beside your file manager. A signature that passed a friend's SSC upload last year may fail today if you are on UPSC OTR or if the board tightened validation.

If background reads grey at 100% zoom even when pixels match, read background not white rejected explained before your next export — grey scan edges fail some validators the same way off-white photo backgrounds do.

Quick measurement checklist

1. Locate the exact file you plan to upload — the one in Downloads, not a chat-forwarded copy.
2. Open Properties on Windows, Get Info on macOS, or Details in your phone gallery.
3. Record width × height and KB size in a note.
4. Open the image at 100% zoom and count signature rows if the form requires triple signature.
5. Match every value against the active notification PDF before re-export.

If any step is uncertain, transfer the file to a desktop and measure there. Mobile gallery apps sometimes show resolution labels that reflect display scaling rather than the saved JPG header.

Cause 1: Wrong signature pixel dimensions

Cause 1 is any export whose integer pixel dimensions differ from the required pair. The portal does not accept "close enough," "looks right on paper," or "the cyber cafe said exam size." It reads two integers from the JPEG header and compares them to the bulletin values.

Common sources of Cause 1:

• Reusing a photo-sized canvas. Exporting 630×810 or 200×230 photo dimensions and placing a small signature in the centre fails because the file dimensions are photo dimensions, not signature dimensions.
• Rounded resize boxes. Typing approximate numbers into a generic resize tool produces 139×59 or 351×151 instead of the exact targets.
• Aspect ratio drift. Cropping a scanned sheet without locking signature aspect ratio stretches or squashes strokes after resize.
• Wrong board preset. SSC ~140×60 px targets uploaded to a UPSC ~350×150 px slot fail even when the ink looks perfect.
• Orientation swap. Height and width reversed in the header fail automated checks the same as wildly wrong sizes.

The fix: start from an uncropped scan or photograph of your signature sheet. Crop tightly to ink with white margin, then resize once to the exact pixel pair in the notification. Do not chain multiple saves on the same compressed JPG — each save can drift KB and occasionally dimensions if the editor re-encodes differently.

When UPSC requires three stacked signatures in one file, dimension failure is often coupled with content failure. Follow the UPSC triple signature walkthrough for stacking, ink, and KB — not just width and height in isolation.

Dimension targets by common exam families

Treat the table as orientation only. Numbers shift between cycles — the PDF on your desk is authoritative.

How blur masquerades as dimension failure

Over-compressed signatures sometimes fail quality checks with generic "invalid" text. If pixels are exact but strokes look soft at 100% zoom, the root cause is compression damage, not width and height. See check the photo blurry after resize spec — the same quality-loss pattern applies to thin signature lines after aggressive JPEG saves.

Cause 2: KB or compression damage

Cause 2 covers files whose pixel dimensions read correctly but byte length falls outside the portal's min–max KB window, or whose strokes were destroyed by compression so validators reject them as unreadable.

Signature files are smaller than photos but equally strict about KB floors and ceilings. A 4 KB export may fall below a 10 KB minimum even when legible on a phone screen. A 45 KB export may exceed a 20 KB ceiling on SSC-style forms even when dimensions are exact.

Common sources of Cause 2:

• Compressing before locking pixels. Shrinking file size in a tool that also resizes produces accidental dimension drift.
• WhatsApp or chat transfer. Document mode still re-encodes images; KB and sometimes pixels change in transit.
• Single aggressive quality drop. Jumping from quality 90 to quality 30 in one step turns ink into grey smudges.
• Scanner "small file" preset. Some scanner apps optimize for email, producing illegible signatures under 8 KB.
• Re-saving the same failed export. Each incremental save lowers quality without fixing the original capture problem.

The fix: compress in small steps from a high-quality crop. After each export, read KB on disk and inspect strokes at 100% zoom. Stop when you are inside the stated range with all lines still sharp. If you cannot reach the KB ceiling without blur, recapture with better lighting or a flatter scan — do not keep crushing the same source.

Aim for the middle third of the KB band when the notification gives both min and max. That leaves headroom if the portal recalculates size slightly differently on upload.

KB symptom table

Cause 3: Content, ink, and background failures

Cause 3 is when pixel dimensions and KB both pass automated gates but the image content violates bulletin rules — wrong ink colour, wrong number of signatures, ruled paper visible, shadows, or clipped strokes.

This cause drives many signature rejected multiple times exam form loops because applicants fix KB and pixels while leaving content unchanged. The portal accepts the upload dialog, then rejects during verification, or shows a generic error that sounds like a size problem.

Common content failures:

• Single signature uploaded to a triple-signature requirement. UPSC OTR is the flagship example — one row of ink in a correctly sized file still fails.
• Blue ink on a black-only form. Banking and UPSC often specify black; navy gel scans as grey-blue and fails review.
• Ruled notebook paper. Horizontal lines read as background contamination after compression.
• Clipped flourishes. Wide underlines cropped off at resize make signatures unreadable at verification zoom.
• Stamp or digital overlay. Signatures must be handwritten on paper unless a future notification explicitly allows otherwise.

The fix: re-sign on plain white paper with the correct ink colour. Leave margin on all sides. Photograph or scan with even lighting and a closed scanner lid. Crop to ink, resize to exact pixels, compress to KB band, then verify content at 100% zoom before upload.

For UPSC-specific stacking and ink rules, see the same walkthrough linked above — especially three rows in one file versus three separate uploads on other boards.

Ink and background quick check

The one-pass fix workflow after repeated rejection

Stop uploading until you complete this sequence once. Partial fixes between uploads reset nothing.

1. Archive failed exports in a folder labeled do-not-upload so you never attach them by habit.
2. Re-capture source — fresh signature sheet, black ink, plain paper, even light.
3. Crop once to ink with margin; do not resize yet.
4. Resize once to exact notification pixels; verify width and height on saved file.
5. Compress iteratively to KB band; verify strokes at 100% zoom after each step.
6. Rename the final export (signature_v4.jpg) so the portal cannot cache an old attachment.
7. Upload from a fresh browser session if the form still shows the previous error after a verified-good file.

If step 4 and step 5 fight each other — dimensions correct but KB only works when blurry — return to step 2 with a cleaner capture. No amount of re-compression fixes a smudged original.

Keep photo and signature workflows separate. A fixed photograph does not repair a signature file still failing Cause 3. Export each from its own source capture.

Common mistakes that keep signature rejection looping

• Re-uploading the same JPG. The validator reads the same integers again. Re-export from source, rename, retry.
• Fixing photo first. Photo pass does not imply signature pass — measure signature independently.
• Trusting cyber cafe labels. "Exam signature size" on a receipt may mean last year's SSC spec, not your UPSC cycle.
• Using passport resize presets for signatures. Photo aspect ratios and pixel pairs differ from signature boxes.
• Switching browsers without changing files. Useful for session bugs, useless for dimension and KB failures.
• Assuming one rejection reason. Log width, height, KB, and content checks each attempt so you know what changed.
• Signing on soft surfaces. Notebook covers curve paper and create shadows that read as background noise.
• Tracing in pencil then inking. Eraser marks photograph as grey patches validators flag.
• Ignoring minimum KB. Compressing to the smallest possible file triggers low-quality rejection on many boards.

None of these require a new identity document if your handwriting is readable. They require discipline on capture, export, and measurement.

Mobile upload and file-transfer pitfalls

Mobile browsers sometimes attach a downscaled gallery copy even when the full-size file exists on the device. Export on desktop when possible, or download an explicit signature JPG from your tool, then transfer via cable or cloud without chat recompression.

Attachment pickers — "Choose photo" versus "choose file" may pull different assets. Prefer file picker pointed at Downloads where you saved the measured export.

Orientation tags — Rarely, EXIF orientation confuses viewers; width and height in Properties remain authoritative. If rotation looks wrong after upload preview, rotate in a desktop editor and re-save baseline JPG, then re-measure.

Low-data mode — Some phones substitute optimized copies on slow networks. Upload from Wi-Fi after confirming file size and dimensions on disk.

When automated gates run in upload, servers typically parse JPEG headers before content review. Fix pixels and KB first — then ink, background, and signature count — in that order.

Board-specific notes when rejection repeats

The same JPG export strategy does not transfer between boards. Treat each notification as a fresh spec sheet even when vocabulary repeats.

SSC and IBPS banking signatures

SSC-family forms typically expect a single signature near 140×60 px with a 10–20 KB band on many cycles. The most common repeated rejection pattern is an oversized canvas — applicants export photo dimensions and centre a tiny signature inside. Validators read file width and height, not ink footprint.

Black or blue ink depends on the bulletin line — never assume blue because a bank KYC form accepted it last month. Compress gently; SSC floors reject 6 KB files that look fine on mobile.

If you already passed SSC photo upload, do not reuse that photo resize preset on the signature slot. Photo and signature are sibling uploads with different pixel pairs on the same PDF.

UPSC OTR triple signature

UPSC adds a content rule photo uploads never carry: three stacked signatures in one JPG. A signature rejected multiple times exam form loop on OTR often means one row of ink in an otherwise perfect file. Re-read the notification sentence about signature content before touching pixels again.

Follow the upsc triple signature complete walkthrough for physical signing layout, black-ink capture, and square-photo separation. UPSC also enforces file naming on many cycles — photo and signature literals matter after pixels pass.

Railway, state PSC, and niche boards

Railway notifications sometimes alternate scan-only language with camera-allowed footnotes cycle to cycle. State PSC bulletins publish signature heights from 150×50 px through 200×80 px without standardizing vocabulary across states.

When rejection repeats on a niche board, screenshot the portal error beside your Properties panel and compare to the PDF table row for signature — not the photo row above it. Coaching centre WhatsApp forwards often mix rows from different exams.

Documenting each attempt so the loop stops

Repeated rejection without notes feels like random failure. A simple log breaks that illusion:

Fill the row before every upload. If width, height, and KB are identical on attempts 2 and 3, you did not change the file — the portal did not change its mind. Change one variable per attempt: either re-export from source or fix content, never both blindly.

Store failed exports outside Downloads. Name passing exports with cycle id: ssc2026_sig_v3.jpg. Delete ambiguous signature_final.jpg files monthly.

When helping family members, watch for generational habits — single-line stamp signatures, blue pens from office desks, or ruled notebooks carried from bank KYC visits. Those habits cause Cause 3 while the applicant chases Cause 2 compression tweaks.

PhotoFix is an independent utility, not affiliated with any exam board. Requirements change between cycles; the official notification remains final authority. Use this guide as a practical sequence, then cross-check numbers on the day you submit.

When to escalate beyond self-service fixes

If width, height, KB, ink, background, and signature count all match the notification after independent verification, and the portal still rejects:

• Screenshot the error with timestamp and try an incognito session with the renamed file.
• Confirm you are on the correct exam cycle URL — old registration links sometimes point at prior-year validators.
• Check whether the portal expects a specific file name (signature.jpg only).
• Contact the helpdesk with your measured width, height, and KB — vague "it won't upload" tickets get slower responses.

Escalation is rare. Most repeated signature rejections resolve when applicants stop retrying the same export and run the measurement checklist once.

Iterative compression without entering Cause 2 again

When KB is high but pixels are correct, lower JPEG quality in five-point steps — 85, 80, 75 — saving a new file each time. Open each save at 100% zoom before checking KB. Stop at the first export that lands inside the bulletin band with strokes still continuous.

If quality 75 still exceeds maximum KB, reduce canvas only after confirming notification allows no smaller pixel box — some boards fix pixel pairs strictly. Never shrink pixels to chase KB unless the bulletin permits a range of widths and heights.

When quality must drop below 70 to hit KB, abandon that capture and recapture with darker ink and cleaner white background instead. Cause 2 driven by over-compression mimics Cause 3 unreadable signatures at verification.

Pair compression checks with the same blur-check thinking used for photo resize — thin lines blur before square photo regions show obvious blockiness.

Session cache and portal quirks on repeat upload

Some exam portals cache the last failed attachment filename in session storage. Symptoms: you fixed the file, re-uploaded, and the same error returned instantly without progress bar delay — suggesting the server never parsed your new bytes.

Rename every corrected export. Close the browser completely. Reopen notification URL in a private window. Select the renamed file from disk with file picker, not drag-drop from chat preview.

Disable browser extensions that block scripts on government domains — rare, but upload widgets sometimes fail silently and leave old file handles attached.

If the portal offers a remove or clear signature button, use it before attaching the next file. Stacking multiple failed attempts in UI state confuses applicants who think the latest pick replaced earlier picks automatically.

Photo versus signature field mix-ups

Repeated rejection sometimes means the photo JPG sits in the signature field — identical error text on both fields on some portals. Compare filename and Properties before attach: signature files are wider-than-tall or short landscape rectangles; photos are tall portrait or square for UPSC.

Upload photo first or signature first per notification order if specified. Some sessions timeout when you spend twenty minutes fixing signature while photo sat half-complete — refresh and re-login before final submit.

When both fields fail, fix one file completely before opening the other field's editor tools. Parallel edits increase swap risk between Downloads files named signature(1).jpg and signature(2).jpg.

Night-before-deadline recovery sequence

When the exam form closes tomorrow and signature failed twice tonight, do not sleep on a third identical upload. Spend twenty minutes on measurement log, twenty on re-capture if content failed, twenty on resize and compress from uncropped source. Sleep beats fourth blind retry that triggers portal lockout on some boards.

Keep photo upload frozen until signature passes if the portal validates photo first — fixing signature while photo session expires wastes both.

Screenshot bulletin signature row on phone in case portal text differs from PDF wording — helpdesk tickets with bulletin screenshot resolve faster than vague invalid signature messages.

Final verification before you consider the job done

Pause thirty seconds before upload or before leaving the shop. Re-read Properties or ruler measurements one last time. Applicants who skip this beat themselves after walking away — signature field still had yesterday file selected, or shop bag contained test print not final sheet. Tell one family member which file on USB is the passing export — second pair of eyes catches wrong attachment better than tired applicant reflex. PhotoFix builds exports to published spec; exam boards and print shops still change rules between cycles. Re-open the official notification on submit day — not from memory alone.

FAQ

What causes a signature rejected multiple times exam form error? The portal keeps reading the same failing file properties — wrong pixel dimensions, KB outside the stated band, wrong format, or content that violates ink and signature-count rules. Re-uploading unchanged files repeats the failure.

I fixed KB — why does it still reject? KB and pixels are independent checks. A file can meet KB limits while width or height are wrong, or while blue ink and grey backgrounds fail content review. Measure all three before the next upload.

Does renaming the file help? Yes when browsers cache a failed attachment name. Renaming each corrected export (signature_final_v2.jpg) forces a fresh pick. Renaming without re-exporting fixes nothing.

Can I reuse my passport photo crop for signature? No. Signatures need their own pixel box and capture — usually a scan or photo of signed paper, not a face photo with a signature pasted on.

Why does UPSC reject my signature when file size is correct? Most often because the image contains one signature instead of three stacked rows, or because blue ink was used. Less commonly, over-compression blurred strokes.

Should I scan or photograph my signature? Either works if lighting is even and background stays white. Scanners fail when the lid is open; phone photos fail when shot at an angle. Verify at 100% zoom either way.

How many times should I retry before starting over? After two failures with the same file, stop uploading. Re-measure on disk. If pixels, KB, and content already match the notification, rename and try a fresh session — otherwise re-export from source.

Does changing ink colour fix a dimension error? No. Ink fixes Cause 3 content failures. Dimension errors need exact pixel width and height from a fresh resize.

Can WhatsApp document mode send a compliant signature? Unreliable. Chat apps re-encode JPGs. Use cable, AirDrop, or cloud download and re-check Properties at destination.

Is a digital signature drawn on screen accepted? Only if the active notification explicitly allows it. Most Indian exam boards still describe handwritten signatures on paper, photographed or scanned.

What file format do exam portals expect? Baseline JPG is the safe default. PNG and HEIC often fail before parse or show generic invalid errors.

How long does a clean re-export take? About ten to fifteen minutes — five to sign and capture, five to crop, resize, compress, and verify. Faster on repeat if you kept an uncropped source scan.

Fix it now

Upload your signature sheet capture once. PhotoFix crops to the published pixel box for your exam preset, compresses into the KB band without crushing thin strokes, and exports a baseline JPG you can verify at 100% zoom before upload. Measure width, height, and KB on the downloaded file — then rename and submit in a fresh browser session so a signature rejected multiple times exam form loop ends on the next attempt.

Keep an uncropped source scan until the portal accepts the upload. Repeated saves on the same JPG push you from a solved dimension fix into compression damage on the next try. One careful export from source beats five incremental saves on an already failing file.