PDF Studio

PDF Studio is a dedicated file workspace, not a CRM screen. Start by uploading or creating a PDF record, then choose a task: organize pages, edit and annotate, protect and redact, OCR and extract, compare, convert, compress, sign, or export evidence. Sales CRM, Contract Hub, and Document Sign are optional connected workflows.

• Standalone capture: new PDFs no longer auto-attach the first CRM account, deal, or envelope
• Searchable PDF Tool Catalog for Start, Organize, Edit and review, Protect, Extract and AI, Export, and Evidence workflows
• Document queue, source preview, page navigation, source download, and operation queue
• Merge, split, extract, insert, delete, reorder, page numbers, headers and footers, stamps, annotations, forms, OCR, compression, conversion, and signed-PDF artifacts
• Validation for page counts, split ranges, file type, non-empty uploads, and guarded source metadata
• Each cataloged PDF tool names its user control, validation rule, app API route, and MCP target
• Every screen in the module reads in ten languages: the tool names and taglines, the panels, the page organizer, the review rail, and the error messages

• Optional connected workflow fields are hidden behind an explicit expander and remain blank until the user chooses them.
• PDF Studio loads only PDF documents, operations, stamp assets, and PDF readiness by default; CRM, deal, and signing lookups are fetched only after opening the optional connected workflow.
• The number of pages in a document is counted from the file itself when it is uploaded, not taken from whatever the browser reported. Where it cannot be counted, because the file is encrypted, was truncated in transit, or is larger than the measuring limit, Atlas records that the count is not known rather than assuming one page. A split plan for such a document says the page count is unknown instead of quietly offering a single part.
• Stamping a document with an image requires an image. The control is offered only once your workspace holds at least one stamp asset, and it says so when there is none. It used to be available always, and with no asset behind it the operation completed, rewrote the document and drew nothing visible on the page.
• Redaction and protection actions remain governed; unsupported permanent redaction fails closed rather than producing unsafe overlays.

1. 1Open /pdf-studio and search the PDF Tool Catalog for the action you need.
2. 2Use Capture to create a standalone PDF record or upload a source PDF.
3. 3Open Documents to preview the source, search text, queue operations, and download artifacts.
4. 4Use the optional connected workflow only if the PDF should appear in a CRM, contract, or signing context.
5. 5Use Connected workflows at the bottom for an explicit handoff to Document Sign, Contract Hub, CRM, or Capture.

Does PDF Studio depend on Sales CRM?

No. PDF Studio is standalone by default. CRM, Contract Hub, and Document Sign links are optional and explicit.

Is it Acrobat-complete?

Atlas now covers a broad native operation set, but full Acrobat parity still requires more visual editing breadth, provider-backed OCR and conversion proof, and browser and mobile visual QA evidence before we claim 100%.

Why are some redaction actions blocked?

Permanent redaction must remove underlying content and hidden data. If the sanitizer proof is not ready, Atlas keeps the file safe by blocking permanent apply and offering review artifacts instead.

Is PDF Studio available in my language?

In the browser, yes, in all ten languages Atlas supports. The tool names and taglines, every tool panel, the page organizer, the review rail, the version history and the error messages read in the language you have chosen. Two things stay in English on purpose: the public tool pages, whose web addresses are built from the English names, and the language you pick as a translation target, which is the value sent to the server rather than the words on the button. On the phone the picture is partial and worth stating plainly: the headings, the guidance paragraphs, the empty states and the labels a screen reader speaks read in your language, while the names of the queued operations and the messages shown after an action succeeds or fails are still English. That remainder is counted by a test rather than estimated, so it can fall but cannot quietly grow. Every translation is machine-produced and waiting for a native reader, and the language settings screen says so for each language rather than calling them approved.