> For the complete documentation index, see [llms.txt](https://docs.inji.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inji.io/inji-verify/functional-overview/end-user-guide/verify-by-uploading-the-qr-code.md).

# Verify by uploading the QR Code

## Overview

This guide explains how to verify credentials by uploading documents containing QR codes when camera scanning isn't available or practical. The upload feature supports PDF, JPEG, JPG, and PNG files, and can process higher-density QR codes (up to version 32) that may exceed camera scanning capability.

Once uploaded, Inji Verify extracts the QR data using the PixelPass library and validates the credential using the Verification SDK, displaying the full credential details upon successful verification.

## Verify by uploading the QR Code

**Upload QR Code:**

1. Go to the Inji Verify portal and select the tab **Upload QR Code** where the Upload QR code section will come up and click on the **Upload** button to initiate the process.

<figure><img src="/files/TFzQayfJqRx59ka4R5VO" alt="" width="500"><figcaption><p>Desktop View</p></figcaption></figure>

<figure><img src="/files/kC3psP8qaDwDSe6CqNyr" alt="" width="150"><figcaption><p>Mobile View</p></figcaption></figure>

2. Click on the **"Upload"** button on the **Upload QR Code** Page as you select the option to upload a file containing the QR code or credential document you wish to verify from your device's (Desktop or Mobile browser) file explorer. Click on the file to proceed.
3. **How is QR Code decoded and verified once you have uploaded it?:** Inji Verify passes the QR data from the uploaded file to the Pixel Pass library for processing.
   * The QR data is passed to the Pixel Pass SDK for decoding.
   * Pixel Pass returns the decoded data to Inji Verify for further processing.
   * Inji Verify then verifies the decoded data using the Verification SDK.

<figure><img src="/files/AQpiKlUqX1jWLkOoWd1i" alt="" width="500"><figcaption><p>Desktop View</p></figcaption></figure>

<figure><img src="/files/fj5aqtQj9W65EuGmTuvF" alt="" width="150"><figcaption><p>Mobile View</p></figcaption></figure>

4. **Display Credential Details:** - Upon successful verification, Inji Verify retrieves the display properties of the credential and presents the details on the portal's interface.

<figure><img src="/files/1PQ8YNt2GBnKOIftEBkA" alt="" width="500"><figcaption><p>Desktop View</p></figcaption></figure>

<figure><img src="/files/Qph0m9q067CGeuUhIpVl" alt="" width="150"><figcaption><p>Mobile View</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.inji.io/inji-verify/functional-overview/end-user-guide/verify-by-uploading-the-qr-code.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.