GitHub Education verification image becomes blurry after capture on multiple devices

[patriciodiazdiaz]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Evidence and Image Capture

Hi everyone,

Hello,

I am trying to apply for GitHub Education Student Benefits and my application has already been rejected three times.

The issue is not that my original document is blurry. The problem occurs after pressing "Capture photo".

What I tested:

• iPhone
• iPad
• Mac
• Safari
• Chrome
• OBS Virtual Camera with a high-resolution digital document
• Multiple document types (student ID, transcript, enrollment letter, class schedule, etc.)

In every case:

1. The image is clear and readable before capture.
2. After pressing "Capture photo", the captured image becomes noticeably blurry/compressed.
3. The application is later rejected with OCR-related errors indicating that my name, institution, and date could not be read.

My institution is recognized by GitHub Education.

I have already been rejected three times despite testing different devices, browsers, and document types.

Has anyone experienced the same issue recently, or is there a known workaround?

Thank you.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[roshhellwett]

Skip the camera entirely. GitHub Education supports document upload as an alternative. Just go back to the verification page, look for the "Upload a document instead" option (usually a small link below the camera view), and upload a clean PDF or high-res JPG of your enrollment letter or student ID directly.

That bypasses the compression completely and OCR works fine on a directly uploaded file....

[patriciodiazdiaz]

Thank you for the suggestion.

Unfortunately, I do not see any "Upload a document instead" option in the current GitHub Education verification flow.

I have tested:

• iPhone
• iPad
• Mac
• Safari
• Chrome
• Multiple document types

In all cases, the verification page only provides camera capture and does not offer a file upload alternative.

Could you please share a screenshot of where that option appears in the current verification process?

Thank you.

[roshhellwett]

1. Screenshot your document as a PNG
Open your PDF fullscreen, use Snipping Tool (Win+Shift+S) or macOS Cmd+Shift+4 to capture it as a sharp, high-res PNG. Use that as your "camera photo" — OCR reads clean screenshots just fine.

2. Browser console trick (desktop only)
Open DevTools (F12 → Console) and run:

document.querySelector("#dev_pack_form_camera_required").value = 'false';

This disables the camera-required flag and surfaces the file upload button.

3. GitHub Support ticket
If nothing above works, skip the automated flow entirely. Open a ticket at https://support.github.com — attach your documents and a human will review manually. Don't use "verification failed" as the subject, use something like "GitHub Education student benefits" instead.

[patriciodiazdiaz]

Thank you for the suggestion.

I inspected the page and found the hidden field dev_pack_form_camera_required. I changed its value to false, but the interface did not change.

I also checked the DOM and there is currently no input[type="file"] element or upload control present.

It seems the current GitHub Education flow is camera-only.

The main issue remains that the image becomes blurry after pressing "Capture photo", even when using a high-resolution digital image through OBS Virtual Camera.

[roshhellwett]

Support ticket this is the real path forward
The automated flow is clearly broken on GitHub's side. Go to https://support.github.com and open a ticket. Don't mention "verification failed" use a subject like "GitHub Education student benefits image quality issue during verification". Attach your document directly to the ticket. A human reviewer can manually approve it.

[abdelkaderbelkacemi13]

I am facing the same issue, i was a verified student until today, nothing work

[Usman-Amin-AI]

Thank you for providing detailed troubleshooting information.

Based on your description, this appears less like a document eligibility issue and more like a potential problem with the image capture and processing pipeline. The fact that the document is clear before capture but consistently becomes blurry immediately after pressing "Capture photo" across multiple devices, browsers, and document types suggests that image compression, resizing, or post-processing may be reducing the quality before OCR verification occurs.

The troubleshooting you've already performed is quite comprehensive:

• Multiple devices (iPhone, iPad, Mac)
• Multiple browsers (Safari and Chrome)
• Multiple document types
• High-resolution digital source via OBS Virtual Camera

Given those tests, it seems unlikely that the issue is related to camera hardware or document quality on your end.

A few questions that may help identify whether others are experiencing the same behavior:

1. Does the captured preview appear blurry immediately after capture, before submission?
2. Are the OCR rejection messages consistently indicating that specific fields (name, institution, date) cannot be read?
3. Have other applicants noticed a decrease in image quality after the capture step during the past few weeks?

If the issue is reproducible across different platforms, GitHub may want to investigate whether recent changes to image processing, compression settings, or OCR validation thresholds are affecting document verification.

Since your institution is already recognized and you've received multiple rejections despite providing valid enrollment documentation, it would be helpful if a GitHub staff member could review whether this is an account-specific issue or a broader problem affecting the verification workflow.

Thank you for documenting the issue so thoroughly. Hopefully, additional reports from other users can help determine whether this is a wider bug in the evidence capture process.

[patriciodiazdiaz]

Thank you for your detailed analysis.

To answer your questions:

1. Yes. The captured preview becomes blurry immediately after pressing "Capture photo", before submission. The image is clear before capture, but the preview shown by GitHub after capture is noticeably lower quality.

2. Yes. The rejection messages consistently indicate that my name, institution, and current date could not be verified or read.

3. Yes. I have found multiple recent discussions from other applicants reporting similar behavior, specifically that image quality appears to degrade after the capture step and that the current verification flow only allows camera capture.

Additional troubleshooting performed:

• Tested on iPhone, iPad, and Mac.
• Tested on Safari and Chrome.
• Tested multiple document types.
• Tested using OBS Virtual Camera with a high-resolution digital document.
• Inspected the verification page and confirmed that the current flow does not expose any file upload control.
• The issue remains reproducible across all tested devices and browsers.

Based on these results, I believe the problem may be occurring during the capture, compression, or image processing stage rather than being related to the source document itself.

I have already received three verification rejections despite providing valid enrollment documentation from a recognized institution.

Thank you again for your assistance.

[abdelkaderbelkacemi13]

Thank you for your detailed analysis.
i am also facing the same problem, to answer your questions :
1- yes the photo become blur directly after pressing "capture " before the submission.
2- Yes, the rejection messages consistently indicate that my name and current date could not be verified and unreadable.
3- yes, many students and staff are facing this problem

[patriciodiazdiaz]

Update:

I have now confirmed that:

• The institution is recognized by GitHub Education.
• My academic email is valid and verified.
• I have been rejected 3 times.
• I tested multiple document types (enrollment certificate, student portal evidence, etc.).
• I tested on iPhone, iPad, and Mac.
• I tested Safari and Chrome.
• The document is sharp and readable before pressing “Capture photo”.
• Immediately after capture, the preview becomes blurry and lower quality.
• The rejection consistently indicates that my name, institution, or current enrollment date cannot be verified.

At this point, the issue appears related to the image capture/processing workflow rather than document validity.

Has any GitHub staff member seen similar reports recently?

[abdelkaderbelkacemi13]

many of us students/staff are facing this problem, GitHub must fix this camera capture problem asap.

[tanvishinde017]

Hi @patriciodiazdiaz,

You're not the only person reporting this kind of behavior recently. Based on your testing across multiple devices and browsers, it sounds like the problem may be occurring during the capture/upload pipeline rather than with the original documents themselves.

A few things that might help narrow it down:

• Does the preview immediately after capture already appear blurry, or does it only become blurry after submission?
• Are you using the front camera or rear camera on mobile devices?
• Have all three rejections mentioned OCR-related issues (name, institution, or date not readable)?
• Approximately how long do you wait between applications?

Since your institution is already recognized and you've tested multiple document types, this doesn't sound like a typical eligibility problem. It sounds more like an image quality or compression issue.

Hopefully the Education team can investigate whether there have been any recent changes to the evidence capture flow. A direct PDF upload option or higher-quality image preservation would likely help applicants in situations like this.

For privacy, avoid posting screenshots that contain personal information.

[syedahmedx3]

💡 The Root Cause: WebRTC Canvas Compression

The viewfinder looks perfect, but the actual capture is blurry because GitHub takes a low-res frame grab from your active WebRTC stream (often capped at 640x480 to save bandwidth) instead of a raw hardware camera photo. When stretched into the preview box, text details blur out, causing the OCR validation bot to fail.

---

🛠️ The Dev Workarounds

1. Kill Camera Permissions (Forces File Upload Fallback)

The simplest fix is to trick GitHub's frontend into thinking your device doesn't have a camera, which triggers the legacy file upload button.

1. Open an Incognito/Private window and go to GitHub's site settings.
2. Set Camera -> Block.
3. Refresh the verification page. When navigator.mediaDevices.getUserMedia() throws a hardware block error, the UI falls back to an uncompressed File Upload option.

2. Use Mobile Rear Camera

If forcing a fallback fails, switch entirely to a mobile device using the primary rear camera lens. WebRTC profiles allocate significantly higher resolution caps to primary rear cameras compared to front-facing selfie lenses or desktop webcams, keeping the text sharp enough to pass the OCR scan.

3. Support Override

If you have been locked out due to multiple rapid rejections, submit your high-res PDFs directly to a human agent via support.github.com/contact/education to bypass the automated validation layer entirely.

[patriciodiazdiaz]

Thank you for the suggestions and additional investigation.

I tested the proposed workarounds and would like to share the results:

• My institution is already recognized by GitHub Education.
• My academic email is verified and has been used for all verification attempts.
• I have now submitted 3 separate applications using different valid enrollment documents.
• I tested on iPhone, iPad, and Mac.
• I tested using both Safari and Chrome.
• I also tested with a high-resolution source through OBS Virtual Camera.

Additional findings:

• The document appears sharp and fully readable before pressing "Capture photo".
• Immediately after capture, the preview becomes noticeably lower quality and blurry.
• The OCR rejection consistently indicates that my name, institution, or current enrollment date cannot be verified.

I also tested blocking camera permissions entirely to see whether a file-upload fallback would appear. In my case, the verification flow remained unchanged and still required the camera capture process.

I additionally checked the GitHub Education support contact flow, but it appears to redirect to the same support workflow and does not provide an alternative document upload method.

At this point, the issue appears reproducible across multiple devices, browsers, and document types, which makes me believe the problem may be related to the image capture or processing pipeline rather than the validity of the submitted documents.

[syedahmedx3]

💡 The Fix: Force High-Res WebRTC Stream

GitHub's system automatically forces your camera stream down to a low resolution (like 480p) the second you hit capture to save bandwidth. This blurs the text and triggers the OCR rejection. Since they disabled the file-upload fallback, you can bypass this by forcing your browser to command a high-definition stream instead.

Please try this step-by-step fix on your desktop or Mac:

---

🛠️ Step-by-Step Console Fix

1. Open the GitHub Education verification page.
2. Open your browser console:
   • Mac: Press Cmd + Option + I and click the Console tab.
   • Windows: Press F12 or Ctrl + Shift + J and click the Console tab.
3. Paste the following code into the console and press Enter:

navigator.mediaDevices.getUserMedia = async function(constraints) {
  if (constraints.video) {
    constraints.video = { 
      width: { ideal: 3840, min: 1920 }, 
      height: { ideal: 2160, min: 1080 }, 
      facingMode: "environment" 
    };
  }
  return Object.getPrototypeOf(navigator.mediaDevices).getUserMedia.call(navigator.mediaDevices, constraints);
};
console.log("🚀 HD Overrides Injected!");

Leave DevTools open, line up your document clearly, and click "Capture photo".

The browser will now intercept GitHub's low-res limit and capture a sharp, uncompressed high-res frame that the OCR bot can read instantly. Let me know if this successfully gets your document approved!

[patriciodiazdiaz]

He behavior remains identical: the document is clear before capture and blurry immediately after capture.

If anyone else is experiencing this issue, please let me know which device/browser combination you are using.

Thanks!

[Schadre]

Good Evening, Is there a solution to this image becoming blurry after capture yet?

[patriciodiazdiaz]

I investigated the issue further using browser developer tools.

The camera stream is negotiated at 1920×1080 and 60fps:

width: 1920
height: 1080
resizeMode: none

However, after clicking “Capture photo”, GitHub generates a JPEG image with a natural size of only:

316 × 177

I verified this by inspecting the generated image element (data:image/jpeg;base64,...) in the browser.

This means the image is being drastically downscaled between the live camera stream and the captured image used for verification.

That would explain why the live preview is clear, while the captured image becomes blurry and OCR consistently fails across multiple devices, browsers and document types.

Has anyone from GitHub Education or Support confirmed whether this capture resolution is expected?

[rmrosi]

I suppose the problem isn't with the camera capturing the document, but with the document validation method! I'm a professor at a Higher Education Institution, I had already been accepted into GitHub University, a revalidation was requested, I uploaded several files (that is, I didn't use the device's camera), but none of the documents were accepted! I've already received 5 rejections and I don't know which document to send anymore. I even sent a copy of my work permit, without success!