All tools
Documents & PDFs

CAN I VIBECODE

Adobe Acrobat Pro?

NOT REALLYA prototype of the interface is possible, but the durable product depends on difficult systems beyond the UI. Build a safer adjacent workflow instead.

BUILD FIRST

  1. A non-sensitive or read-only version of the core experience
  2. A manual review step wherever correctness or trust matters
  3. A narrow companion tool that removes a real piece of work

LEAVE FOR LATER

  1. Regulated decisions, payments, or irreversible actions
  2. Claims of correctness, compliance, or uptime that the MVP cannot support
  3. Sensitive integrations until security, support, and auditability are ready

RESEARCH NOTES

What this tool actually does.

Checked 2026-09-06

Adobe Acrobat Pro (Adobe Inc.; subscription app for Windows, macOS, web, and mobile) is a full document suite for creating, editing, converting, protecting, and signing PDFs. Core capabilities: direct in-PDF editing of text and images (fix typos, change fonts, crop/swap images); OCR that turns scans into searchable, editable text; two-way conversion to/from Microsoft Word, Excel, PowerPoint, and image formats with layout retention; page organization (merge, split, reorder, rotate, crop); commenting, highlighting, and markup for review; permanent redaction of sensitive data; password/encryption and permission controls that prevent copying, editing, or printing; file comparison showing what changed between two PDF versions; e-signature workflows with signing links, status tracking, and reminders; and share links letting reviewers comment without login. Newer releases add an AI Assistant fo

RESEARCHED BUILD PROMPT

Give this to your coding agent.

Build a focused, self-hosted web app that reproduces the core document workflow of Adobe Acrobat Pro: a user opens a PDF in the browser, edits text and images, OCRs scans, converts to/from DOCX/XLSX/PPTX, merges/splits/reorders pages, redacts content, password-protects files, compares two PDF versions, and requests e-signatures with status tracking. User-facing requirements: drag-and-drop upload with a live per-page PDF viewer (PDF.js rendering); clickable text layer for in-place text edits, image crop/replace, and thumbnails for reorder/delete/rotate; an OCR pipeline that makes scans searchable/selectable with highlighted matches; a conversion modal exporting to DOCX/XLSX/PPTX/PNG/JPEG with reasonable layout retention; a redaction tool where users paint regions, preview the blacked-out output, and export with the underlying content permanently stripped; password and permission (print/copy/edit) enforcement on export; a side-by-side compare view highlighting added/removed/changed text; and a signing flow that attaches signature fields, sends a signing link, and shows status. Technical approach: Node.js or Python FastAPI backend; PDF.js for rendering and text extraction; PyMuPDF or pdf-lib for edits, merge/split, redaction, and encryption; Tesseract.js for on-device OCR; Mammoth plus headless LibreOffice (soffice --convert-to) for high-fidelity DOCX/XLSX/PPTX conversion; SQLite for signing requests; ship as a Docker container. Do not copy Adobe branding, logos, proprietary assets, or the Acrobat UI; design an original clean interface. Deliberately out of scope: mobile apps, AI Assistant chat/summaries, PDF Spaces collaboration hub, cloud sync, and batch/watermark automation. The README must cover setup (env vars, LibreOffice dependency, Docker), how each pipeline works, and important limitations (unembedded fonts, OCR accuracy on low-res scans, complex-layout conversion quirks, and redaction caveats about hidden metadata/metadata layers).
Visit the official product page