CAC Document Upload Error — Technical Fixes

A CAC document upload error is the symptom most likely to be misdiagnosed at the iCRP portal. The instinct is to assume the application has failed; the reality is that almost every upload error is a file-format, file-size, session, or browser issue with a portal-side fix. None of the five common failure modes requires legal expertise, no accredited agent earns a fee on this fix, and the diagnostic runs in minutes rather than days.

The point of this article is to walk through the five common failure modes and the matching fix for each. The order is not arbitrary: it starts with the cheapest diagnostic (look at the file) and ends with the most involved (full browser reset). Run the diagnostics in order and stop at the first one that clears the error.

The diagnostic is a ladder: the first three failures are file-side problems, the fourth is a session-side problem, and the fifth is a browser-or-account-side problem. Running the diagnostic in order isolates the failure mode in minutes.

The iCRP Electronic Document Management System (EDMS) accepts a specific list of file formats and rejects everything else. The current accepted formats:

• PDF for every statutory form and document: the memorandum and articles of association, the board resolution, the consent letter, the trust deed, the AG consent letter, the share transfer instrument, audited financials where applicable, the partnership deed where applicable, the certificate of police report and affidavit of loss where applicable.
• JPG or PNG for passport photographs and signature scans.

The portal rejects: DOCX, DOC, ODT, RTF, TXT, and any image-of-text format that has been renamed to .pdf without proper conversion. The portal reads the file header (the binary identifier inside the file), not the file extension; a JPG renamed to a .pdf extension will be detected as a JPG and rejected.

The fix:

• If the source is a Word document, open it in Microsoft Word, Google Docs, or LibreOffice and use the built-in Export as PDF (or Print to PDF) function. Save the PDF and upload that file.
• If the source is a scanned document, scan directly to PDF rather than to JPG. Most scanners and the major mobile scanning apps (Adobe Scan, Microsoft Lens, Genius Scan) offer a Save as PDF option.
• If the file is already a PDF but the portal still rejects it, the cause is more likely Failure 2 (size) or Failure 3 (corruption); move to the next diagnostic.

This failure clears in seconds once the format is correct. It is the single most common upload error at iCRP.

Every upload field at the iCRP portal carries a per-file size cap, shown in the field-level guidance. Statutory forms (PDF) historically sit around the 5 MB ceiling; passport photographs and signatures typically have a tighter cap measured in hundreds of kilobytes. A high-resolution scan of a multi-page document easily exceeds the cap.

The fix:

• For a scanned PDF that is too large, re-scan at a lower DPI. Most scans default to 300 DPI; reducing to 200 DPI typically halves the file size without affecting legibility of text. Reducing to 150 DPI works for clean printed text but starts to soften handwritten signatures.
• For a PDF that is already at a reasonable DPI, run the file through a PDF compression tool. Adobe Acrobat (the paid version), Smallpdf, ILovePDF, and PDF24 all offer free or freemium compress-to-PDF utilities that reduce file size while preserving legibility.
• For a passport photograph that is too large, resize to the portal's stated pixel dimensions and save as JPG with a moderate compression level. The portal's photograph standard is typically 600 by 600 pixels at a colour JPG.

A practical hint: scan documents to PDF as black-and-white where the source paper is monochrome. A black-and-white scan of a signed board resolution is a fraction of the file size of a colour scan and reads just as well at the reviewer's end.

The file has the right extension and the right size but the portal will not parse it. The cause is structural: the PDF's binary header is malformed, the encoding is broken from a partial download, or the file is an image (JPG) that has been renamed with a .pdf extension and is therefore not a true PDF.

The fix runs in two steps:

• Open the file in a local PDF reader on your device (Adobe Acrobat Reader, Foxit, Microsoft Edge's built-in PDF viewer, the macOS Preview app, a mobile PDF reader). If the file opens cleanly, the portal-side cause is likely Failure 4 (session) or Failure 5 (browser); move on. If the file fails to open in the local reader, the file itself is the problem.
• Re-create the file from the source. Re-scan the original paper, re-export from the original application (Word, Pages, Google Docs), or re-download from the original source where the file was emailed. Verify the new file opens cleanly in the local reader before attempting the upload again.

The most common source of this failure is a file shared through a messaging app (WhatsApp, Telegram) that compressed the PDF as an image during the share. Always upload from the original source rather than from a messaging-app version of the file. A document received over messaging should be re-saved or re-exported before upload.

The iCRP portal's session window is typically thirty minutes from the last interaction. A long read of a document inside the same page, a phone call that pulled the user away from the keyboard, or a slow internet connection during the upload itself can all push the page past the timeout window. When the upload finally posts, the portal rejects it with a session-expired error.

The fix:

• Sign back in to the iCRP account at the original portal half (pre.cac.gov.ng for pre-incorporation, post.cac.gov.ng for post-incorporation).
• Open the same case file from the dashboard. The earlier steps in the application are persisted on the case file; only the in-flight upload is lost.
• Re-upload from the step where the timeout caught you. The portal accepts the file as a fresh upload against the existing case file.

A preventive discipline: prepare every file you intend to upload BEFORE you sign in to the portal. The signed-in time should be used for clicking, not for reading or assembling. A pre-prepared file uploads in seconds and the session window is rarely the binding constraint.

The least frequent of the five but the most stubborn. Two underlying causes:

• Browser compatibility. The iCRP portal is built and tested against current Chrome, Firefox, and Edge on desktop. Older browser builds (Internet Explorer, very old Safari versions), unusual configurations (heavy ad-blocker extensions, strict privacy mode that blocks third-party cookies for the portal's payment iframe), and mobile browsers (especially in private-browsing mode) can break the upload flow. The fix is to switch to a current Chrome, Firefox, or Edge build on desktop, disable ad-blockers temporarily for the icrp.cac.gov.ng and cac.gov.ng domains, and retry the upload.
• Post-April-2026 reset and 2FA enrolment. CAC began electronic service delivery from August 2020 and rolled out the full e-certificate format in the portal upgrade between 28 December 2020 and 4 January 2021. The upgrade enacted CAMA 2020 and replaced the older paper-and-counter-collection format with the PDF-on-dashboard format that is current now. Certificates issued from late 2020 onward are PDFs by default — no physical certificate is printed at CAC; the PDF on the iCRP dashboard is the canonical original, and a printed copy is a printed-out version of the PDF. Certificates issued before the rollout exist as scanned paper records; CAC issues a re-typed or scanned PDF version on a certified-true-copy request. After the April 2026 cybersecurity incident the iCRP portal requires every user to reset their password and enable two-factor authentication through an authenticator app before regaining access. Following the cybersecurity incident CAC requires every iCRP user to reset their password and enable two-factor authentication through an authenticator app before account features (including the upload interface) are restored. An account that has not completed both steps will show the dashboard but block the upload action with an authentication or "session not authorised" error.

The fix for the 2FA state:

• Use the password-reset link on the iCRP login page; the reset email lands at the registered address on file.
• Sign in with the new password and complete the 2FA enrolment using an authenticator app (Google Authenticator, Microsoft Authenticator, Authy). The portal walks the QR-code scan and the verification code at first sign-in.
• Once the new password and 2FA are both active, the dashboard returns to its full functionality and uploads resume.

A user who has not been near the portal since before the April 2026 upgrade will hit this failure first thing; the reset step is mandatory and there is no DIY-or-agent split on this part of the framework.

A support ticket is the right move when the five diagnostics have all run and the error persists. The Help and Support link at icrp.cac.gov.ng accepts a structured ticket with:

• A screenshot of the error message exactly as it appears on the portal.
• The case-file reference (visible on the dashboard).
• The filename, the file format, and the approximate file size.
• The browser name and version, and the desktop or mobile operating system.
• The five diagnostics already tried and the result of each.

CAC support response times have historically run between one and three working days for routine technical tickets. Tickets that arrive with the diagnostic checklist already documented resolve faster than tickets that read "the upload does not work".

Adjacent to this article: a payment that hangs at the portal is a different problem with a different recovery, even when it surfaces alongside an upload issue. See CAC payment pending for the Remita-CAC reconciliation diagnostic.

• Do NOT repeatedly retry the same file from the same browser session expecting a different result. Each retry against an unfixed cause consumes time and risks pushing the session past timeout.
• Do NOT pay an informal 'CAC consultant' to 'fix' the upload from their end. An upload is bound to the applicant's iCRP account; no external party can complete the upload without account credentials, and sharing credentials creates a security risk far worse than the upload error.
• Do NOT abandon the case file and start a fresh application. The earlier paid steps and the original references are intact on the existing file; a parallel application consumes fresh fees.
• Do NOT rename a Word document to .pdf and try to upload. The portal reads the file header, not the extension; the rename fools nothing.
• Do NOT skip the post-April-2026 password reset and 2FA enrolment in the hope that the dashboard works without them. The portal does not bypass the security upgrade; account features stay disabled until both steps are complete.