Docqify.app Reviews and Details

Questions & Answers

1. What's the story behind Docqify.app?

   I kept needing to turn a stack of phone photos into one PDF and every tool I found wanted me to upload them first. That felt wrong for documents with my ID on them, so I built one that doesn't. The hardest part was making HEIC work reliably on Android the common decoder library evaluates strings at runtime, which a strict CSP blocks, so it failed silently on mobile for a long time.

2. Which are the primary technologies used for building Docqify.app?

   Next.js and React with TypeScript. libheif compiled to WebAssembly for HEIC decoding, Tesseract.js for OCR, and pdf-lib to assemble the PDF. Decoding runs in a Web Worker pool, and a service worker caches the app shell so it works offline.

3. What makes Docqify.app unique?

   Docqify runs the entire conversion inside your browser. There is no server to upload to, so files never leave your device and that isn't just a promise, it's enforced by a Content Security Policy that makes the page structurally incapable of connecting to another origin. It also handles HEIC from iPhones and adds a searchable text layer using OCR that runs locally, both of which most free converters either skip or charge for.

4. Why should a person choose Docqify.app over its competitors?

   Most converters upload your files to their servers, add a watermark, cap how many files you can process, or ask you to sign up. Docqify does none of those. It's free, has no account, no watermark, and no file limits, and because the work happens locally it also keeps working with no internet connection once the page has loaded.

5. How would you describe the primary audience of Docqify.app?

   Students submitting assignments and applications, job seekers preparing documents, and anyone dealing with forms that require photos merged into a single PDF. It's also used by people who are simply uncomfortable uploading documents containing personal identification to a third-party server.