Need Help Understanding Accepted Document Formats for Student Verification

[MaLeasa]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Verification Help & Guidance

Hi everyone,

Title: Need Help Understanding Accepted Document Formats for Student Verification

I’ve tried verifying my student status multiple times using PNG images via desktop and the camera on my cell phone, but the automated system keeps rejecting my submission. My university provides a “Student Profile” page that includes my active status, class level, term, and student type.

Before I try again, I’d like to confirm what document formats or layouts the verification system can read.

Could someone clarify which document formats or layouts the verification system accepts? I want to make sure I’m submitting the correct file type.

Thank you.

[edwinsatya]

Hi @MaLeasa, The good news is that the file format is almost never the reason for rejection. PNG, JPG, and PDF all get read fine, so switching formats probably won't change anything.

What the automated check actually looks for is three things visible in one single image: your full name, your school's name, and a date that falls inside the current term. If any one of those is missing or hard to read, it rejects the submission no matter what format you used.

That's usually why a "Student Profile" portal page fails. It shows your status, class level, and term, but it's a web page with no letterhead, often no institution name printed on it, and sometimes no date. The system has nothing to tie it back to your school.

Documents that tend to work, roughly in order of preference: a dated student ID card, an official enrollment letter from your registrar, an academic transcript, or a class schedule if your school's name is actually printed on it.

One thing that trips people up more than the document itself: the full name on your GitHub account has to match the name on the document. Go to Settings → Public profile and put in your full name, not a handle or nickname. If your school gave you an academic email, add it and set it as primary before reapplying — a few people have reported that alone fixed it for them. Log out and back in after changing your profile.

For the photo, shoot it in good light with the whole document flat in frame and nothing cropped. And don't merge several documents into one image; the checker handles a single clean document better than a collage.

If you've done all of that and it still fails, open a ticket with GitHub Education Support and mention what you already tried so they can review it manually.

[MaLeasa]

Thank you for your reply. My Student Profile shows all the required items. I've also verified that I made all the changes mentioned in your reply. I received a message that GitHub no longer supports manual reviews.
Again, thank you.

[AUG235772]

Hi @MaLeasa,

The message stating that "GitHub no longer supports manual reviews" means your account application must successfully pass the automated machine-learning (OCR) validation gate to receive benefits.

Since you have already updated your public profile name and verified that your school portal displays your name, institution, and a current date, the rejections are being triggered by structural visual markers that the automated OCR engine flags as high-risk or unverifiable.

Here is exactly how the automated scanning engine parses your upload, why a standard "Student Profile" web page fails despite having the correct text, and how to format it so the machine accepts it.

---

Why the Automated Engine Rejects Web Portals

GitHub’s verification engine uses strict optical character recognition (OCR) and document structure models trained primarily to recognize physical, security-printed academic media (like plastic ID cards or official registrar letters).

When you feed it a desktop screenshot or a phone photo of a web portal layout, it triggers structural red flags:

1. Lack of Formal Letterhead: Portal screens usually display text in generic CSS bounding boxes without an institutional crest, formal header block, or official registrar signature layout. The AI cannot distinguish it from a self-made HTML mock-up.
2. Dynamic UI Text Mismatch: Web pages often truncate names or display dates dynamically (e.g., "Current Term: Fall 2026" instead of an explicit registration date like "Issued on: August 13, 2026"). The parsing bot requires a highly definitive, static chronological anchor inside the text string.
3. Moiré Patterns and Screen Glare: If you are using your phone camera to snap a picture of your computer monitor, the camera sensor captures invisible pixel grid lines (Moiré patterns) and glare. The automation interprets these digital screen patterns as an attempt to spoof the system with a digital copy, triggering an immediate security bypass rejection.

---

Step-by-Step Blueprint to Pass the Automated Scan

To get the machine-learning engine to approve your enrollment status automatically, you must change the visual medium of your document:

1. Convert the Portal into an Official PDF Document

Do not take a standard screenshot or photo of the web page. Instead, force the browser to compile the portal into a clean document structure:

• Open your Student Profile page on a desktop browser.
• Press Ctrl + P (or Cmd + P on Mac) to open the print menu.
• Set the destination printer to "Save as PDF".
• Ensure headers and footers are turned ON in the print settings. This adds your university's portal URL string to the bottom of the page, which provides a verifiable cryptographic signal to the parsing bot.

2. Print and Capture It as a Physical Document

If the automated system explicitly demands a live camera stream capture rather than a PDF file upload:

• Print that generated "Save as PDF" student profile onto a physical piece of white paper.
• Place the printed sheet flat on a dark, high-contrast surface (like a dark desk or floor) in a room with strong, uniform, natural lighting (avoid direct overhead light which creates phone shadows).
• Hold your phone completely flat above the paper and use the live camera interface to snap the frame. The machine needs to see the physical edges of the paper to confirm you are photographing a real document.

3. Enforce the Geographic Network Constraint

The automated script cross-references your browser's current GPS/IP location against your school's official campus coordinates:

• Disconnect from all desktop proxies or VPN extensions.
• If your university campus is nearby, complete the application while physically connected to the campus Wi-Fi network, as this instantly overrides a large percentage of the automated OCR suspicion metrics.

[MaLeasa]

Hello,
I am in the manual verification stage. I passed the initial bot verification after several tries, and I am waiting for the updated acceptance email.

Thank you.