PDF tools that get the job done.

Start with whatever you have: an error screenshot, the exact message, known requirements or only the rejected file. DOTi turns available clues into a checklist without inventing missing rules. Then add the file, review the inspection and continue to the PASS certificate when the supplied requirements are met.

Do not rewrite it. Paste the exact wording or upload a screenshot. Error messages often contain useful clues such as a maximum size, accepted format, page limit or required orientation. DOTi looks for those clues and explains them in plain language.

Choose “Enter requirements.” Add any rules you know, such as 5 MB maximum, PDF format, 10 pages or portrait orientation. If you know nothing yet, check the upload instructions on the receiving portal before changing your document.

The platform name is optional. It gives DOTi context and personalizes the PASS certificate, but it is not sent anywhere. You can write a general description such as “university portal” instead of a specific name.

The file contains more data than the portal allows. High-resolution images, scans and embedded fonts are common causes. Ninjitzu PDF compares the current size with the stated limit and, when the repair engine is enabled, will reduce unnecessary data while protecting readability.

Changing a filename extension does not convert the file. A document named “form.pdf” may still contain another format or be damaged. Ninjitzu PDF checks the actual browser-reported file type and compares it with the required format.

Portrait pages are taller than they are wide. Landscape pages are wider than they are tall. Some portals require every page to use one orientation. Use Rotate PDF to correct page orientation before uploading.

Size is only one rule. The portal may also restrict page count, dimensions, encryption, filenames, orientation, PDF version or damaged content. Paste the complete rejection message whenever possible so DOTi does not miss a second requirement.

Confirm the portal’s published upload rules, try a simple filename using letters and numbers, and make sure the file opens normally on your device. Then enter the known requirements manually. A portal can also fail because of its own temporary technical problem.

No. Document processing is designed to run locally in your browser. Your file is not sent to Ninjitzu PDF’s servers. Supabase and Stripe are reserved for account, subscription and payment status—not document processing.

Once the production PWA and its required processing modules have been cached, supported local tools can continue working without sending the document to a server. Payment and account verification still require an internet connection.

The free workflow does not keep a server copy. Temporary browser memory is released when you close or reset the workflow. Future local history in Pro will be stored on your own device and will include controls to remove it.

PASS means the file met the requirements that were supplied to and checked by Ninjitzu PDF. You can download the visual certificate as a PNG with its verification ID and timestamp. It is a useful final inspection, not an official certificate from the receiving organization.

No tool can guarantee rules that a portal does not disclose. PASS confirms the available checks. The receiving portal makes the final decision and may have hidden rules or temporary technical problems.

Yes. On supported mobile browsers, the share sheet can include the file directly. On desktop, Ninjitzu PDF opens WhatsApp with a prepared message; download the file first and attach it to the conversation.

No. Browser-based processing creates a new downloadable result. Your original file remains on your device unless you choose to replace or delete it yourself.