Changelog

The sign-in form has a 'Forgot password?' link. We email you an 8-digit code, you pick a new password, and you're signed in. No support ticket needed. One thing worth knowing if you bought a license: your license key already works as your password. It starts with OPDF- and sits in your purchase receipt email, so you may not need a reset at all. The sign-in form, the reset screen, and the reset email all point this out now.

If you kept a tab open while we shipped a new version, OxygenPDF could reach for a file from the old build that no longer exists and show a 'Something went wrong' screen — the loading-animation stylesheet was the usual culprit. It now catches that case and quietly refreshes to the current version, dropping you back where you were. Sign-in got a fix too: password managers like iCloud Passwords now put your saved email and password straight into the login form.

Adding a watermark, header, footer, or page stamp — or turning text, Markdown, Word, and CSV into a PDF — used to quietly break on characters outside basic Latin. German umlauts typed on a Mac were the worst offender: the diacritic comes through as a separate combining mark that the old font could not encode, so the whole export failed. The text tools now embed real Unicode fonts and normalize your text first, so umlauts, accented names, Cyrillic, Greek, and CJK (Chinese, Japanese, Korean) render properly. Arabic, Hebrew, Hindi, and Thai are supported too, with right-to-left and complex-script shaping handled on a best-effort basis. The same fix reaches the PDF editor and chat form-filling, and scanned documents in non-Latin scripts now keep a searchable text layer instead of dropping it. Fonts for non-Latin scripts download only when needed and are cached; your files never leave your browser.

The RSVP speed reader now opens .md and .txt files alongside PDFs, or you can paste raw text straight in from a new tab. Markdown gets its syntax stripped first — headings, links, bold, lists — so you read the actual prose instead of flashing past # and ** one word at a time. Plain text is split into sections so the preview panel and jump-to-page keep working on long documents. It all still runs in your browser; nothing is uploaded.

The regenerate button on a visual-HTML chip used to silently re-run with the same quality tier you originally picked, which meant if Basic came out flat you had to start a new conversation to try Best. The button is now a small menu — pick Basic, Quality, or Best directly from the chip and the new build runs at the tier you chose (and the chip subtitle updates to match so you can tell at a glance which tier produced the result). The cache is always busted on regenerate, so a tier you already tried genuinely re-runs against the model rather than handing back a stale result.

The assistant occasionally over-extracted a "Save to thread memory?" chip when you replied with just "thanks" or "ok cool" — fabricating a preference you never actually stated. The chat prompt now hard-bans memory suggestions on social acks and explicitly forbids inventing facts the user hasn't spoken, and a server-side filter drops any memory chip that lands on a pleasantry-shaped turn regardless of what the model emitted. Saying thanks no longer triggers a memory pill.

Visual HTML recreation now asks one extra question after you pick 'Visual recreation': Basic, Quality, or Best? Each level runs through a different AI model behind the scenes — Basic is fastest and cheapest, Best is slowest but reads design-heavy pages the most carefully. The chip subtitle shows which tier produced the result so you know what you're paying for, and the regenerate button reuses the same tier you originally picked. Replaces the previous three-pass refinement loop (which was producing modest gains for a lot of extra cost). The underlying prompt also got a full rewrite — the AI now produces Tailwind-CDN-based responsive HTML with semantic tags and proper design fidelity instead of hand-rolled blocky CSS with US-Letter page dimensions.

When you asked the assistant to convert a PDF to Word or HTML, it sometimes wrote "let me ask a couple of quick questions" but forgot to actually emit the wizard — the bubble would just sit there with the four generic follow-up chips (Explain more / Give an example / …) underneath, which read as a broken UI. The model now gets a hard prompt rule against promising clarifications without emitting the matching directive, and a server-side safety net catches the misfire by inferring the right wizard format from your message and recovering the wizard inline.

When you asked to convert a PDF to Word or HTML, the chat assistant used to show a flat list of 3-4 options you had to read and commit to in one click. Re-deciding meant editing your message or starting over. The new wizard walks you through 1-2 short questions inline in the bubble — back-navigable, fully frontend (no extra AI round-trips per question), and the final pick writes the right export shape directly to the message. Markdown and text still skip the wizard since there's only one sensible output for those.

When a scanned PDF gets a 'give me as html' request, the chat assistant now offers four routes instead of three. The new option uses a vision AI pass to rebuild the design as a real webpage with CSS — colors, gradients, custom typography, the works — instead of stripping it down to a semantic export. Click it and the screenshot-to-code pass kicks off automatically: no second click required, the chip shows a spinner while it works, then flips to a download when ready.

Gemini 2.5 Pro is strong on screenshot-to-code but it makes specific mistakes some PDFs trip over. The new Replicate chip routes the same task through Qwen2.5-VL by default — different model class, different failure modes, sometimes a better fit for a given design. Sits alongside the Gemini chip so you can A/B the two on the same PDF without re-uploading. Backend is parameterized via env vars so swapping to DeepSeek-VL3 or any other Replicate VLM takes a config change, not a redeploy.

Word documents can't render modern CSS, which means infographics, posters, and Canva-style exports always lose their visual chrome on a Word export — no matter how clever the converter. HTML can carry all of it. The new chip sends the source PDF to Gemini 2.5 Pro and asks for self-contained HTML+CSS that visually recreates the design: gradients, custom typography, decorative shapes, layered illustrations. Cropped images get inlined as base64 data URLs so the .html opens in any browser with nothing broken. Sits next to the standard HTML chip so you can pick semantic-text or visual-reconstruction depending on what you need.

The previous "page-perfect" chip just embedded each PDF page as a PNG inside the docx. Better than nothing visually, but you couldn't edit, copy, or search anything. The new converter extracts every text item from the PDF via pdfjs with its real (x, y) coordinates and emits one absolutely-positioned paragraph per item in a docx sized to match the source. Font size and bold/italic come along. Result: text lands where it belongs, and you can edit it. v1 ships text only; image extraction and colors land in follow-ups.

Some PDFs are infographics, posters, designed layouts where every arrow, gradient, and font choice matters. Word documents can't reproduce that as vector content — the decorative chrome dies in any text-based conversion. The new chip skips the OCR pipeline entirely: each PDF page renders to a high-resolution image client-side and embeds in the docx as a full-page picture. The result looks identical to the source. Trade-off is honest: editable text is gone, but visual fidelity is total. Sits next to the other two chips so you can pick the one that matches the document.

Mistral OCR is fast and cheap but it flattens multi-column layouts, breaks callout boxes, and treats key-value pairs as random sentence fragments. The new chip hands the whole PDF to Gemini 2.5 Flash and asks for cleanly structured Markdown — heading hierarchy, columns interleaved in reading order, tables reconstructed as tables, callouts as block quotes. It sits next to the standard Word chip so you can pick the cheap fast path or the better slower one depending on the document. Picks up the same embedded images Tier 1 added, so figures still land in the right spots.

Convert an infographic-style PDF to Word in chat and you used to get the headings and paragraphs right but every image came out as literal markdown placeholder text like `` floating between the paragraphs. The OCR pipeline was returning image bboxes but throwing the cropped image bytes away, and the docx converter had no `image` token handler so the marked AST default echoed the raw markdown into the output. Now the OCR pass pulls the cropped image bytes inline, stores them per-image, and the docx/html converters embed them where they belong. Reupload the same PDF and the index gets a free one-time re-OCR so existing chats benefit too.

Ask Chat to convert a PDF to Word and you used to get a wall of unstyled text — headings flattened, paragraphs collapsed, plus whatever OCR typos were baked into the source PDF's text layer. Meanwhile every PDF you upload already runs through Mistral OCR during indexing, which produces clean markdown with real headings, lists, and tables. The conversion path was just ignoring it. Now it doesn't. Ask for .docx, .html, .md, or .txt and the download chip rebuilds the file from the indexed markdown. Heading 1s stay Heading 1s, tables survive, bold and italic stick, and nothing inherits the broken OCR sitting in the source bytes.

Ask Chat to convert a scanned PDF to Word and you'd previously get back an empty .docx with no warning. Now Chat notices the source is image-only and asks under the reply: run OCR and pack the text into a fresh Word doc, embed each page as an image (preserves the look, not editable), or do both — text alongside each page image. Click a chip and the file is built and ready to download in the same bubble. No bouncing into a separate tool. No flipping a toggle to enable OCR. Just pick the outcome and the AI delivers it.

Ask Chat to fill an IRS Form SS-4 (or any PDF whose AcroForm field names look like topmostSubform[0].Page1[0].f1_1[0]) and it actually works. The server tries to match labels by name first since that path is cheap and handles most forms. If nothing matches, the browser takes over: pdfjs reads the visible label text plus every form-widget rectangle on the page, then pairs each label with the closest empty field nearby. Same chip, same download. The old "I couldn't match any of those labels" failure should be a lot rarer.

Chat PDF carries facts forward across turns. Three scopes: things about you (your name, role, how you like answers), things about the PDF (who the contract is for, what kind of report this is), and things about the chat (bullet-only answers, skip the jargon). The assistant proposes saves itself when something durable comes up — you get a Save/Dismiss chip on the bubble, nothing lands without you saying yes. Or type /remember anything you want kept; /memories opens the panel; /forget cleans up. Memories ride into every future prompt so you stop repeating yourself.

Ask "fill this with mock data and give me the markdown file" and you get exactly that: the filled content rendered inline AND attached as a downloadable .md (or .txt) chip — no more misleading "Filled PDF" artifact when you explicitly named a different format. Powered by a new <emit-file> directive on the chat router: when the user names a text output format, the model wraps the synthesized content and the server stores it as a blob, so the download chip lands on the message the same way the PDF chip does. PDF fill requests are unchanged.

When you converted a filled fillable PDF, the values you typed showed up at the corner of each form field instead of where the text actually sits — so labels and values collided in weird ways and the checkbox glyphs ended up clustered at the bottom of the doc. Fixed: pdf-inspector now reads each widget's appearance stream (the same data pdftotext extracts) and places the rendered text at its real position. "Please enter your name: Jordan Lee" reads as one line, not two; checkboxes appear next to the option they belong to; values inside tables sit in their cells.

Convert a filled fillable PDF and the docx came back with internal field identifiers all over it — "Name: Jordan Lee", "Dropdown2: Choice 1", "Option1 Option 1: On", "NameofDependent Name of Dependent: Alex Lee". Those are PDF-internal names that Word users were never meant to see. They're gone now: only the value lands in the doc, at the field's position. Checkboxes also got upgraded — instead of "Option 1: On" you get a real ☑, and unchecked boxes show ☐ instead of being silently dropped. Same fix flows through pdf-to-markdown and the chat-pdf headless converter.

If you fed Chat PDF a filled form and asked for a Word or Markdown export, the values you actually typed (names, addresses, anything non-trivial) came out as ?? J o r d a n L e e — replacement chars where the BOM should have been, and a space wedged between every letter. That was a UTF-16 BE byte order mark the form-field decoder was reading as raw UTF-8. Acrobat and Preview both write filled values that way, so basically every real-world filled form was hitting this. Fixed: the decoder now handles both PDFDocEncoding and UTF-16 BE, the way the PDF spec says it should.

Telling the assistant "convert this to a word doc" used to land you on a "Open in PDF to Word" chip — fine, but you still had to click through, wait for the tool to mount, and click Convert. Now: when you ask, the chip pulses with "Converting to Word…" and resolves to a downloadable .docx right in the bubble. Same for JPG, PNG, WebP, BMP, plain text, Markdown, grayscale, color invert, repair, and annotation removal. Everything that has a deterministic transform with no parameters now auto-executes the moment the model suggests it. Tools that genuinely need UI input (sign, redact regions, image watermark, edit-pdf) still show the click-to-open chip — that's where it's actually useful.

The chat assistant can now run zero-config transforms directly without bouncing you through a tool. Say "rotate every page 90", "lock the form", "compress this", "remove the metadata", or "reverse the page order" and the result downloads in the bubble — same chip you already get for form fills, no second click required. Anything more involved (conversions, signing, redaction, image watermarks, page extraction) still routes through Open-in-tool, so you only pay the UI tax when there's actually configuration to do.

The chat assistant used to know how to do exactly two things — answer questions and fill forms. Anything else (convert to Word, rotate pages, compress, sign, redact, watermark, crop, extract pages…) it would punt on with "I can't do that." No more. The system prompt now ships with the full catalog of fifty PDF-input tools, and the assistant emits an <open-tool> directive whenever you ask for an action it can't run inline. The reply gets a "Open in PDF to Word" (or whichever tool fits) chip — click it and the tool opens fullscreen over the chat with your PDF already loaded. As a side effect: the model can no longer over-eagerly emit <fill-pdf> on a non-fill turn, because <open-tool> takes precedence when both appear, killing the stray "Filled PDF" chip that used to show up after a botched conversion request.

The More menu on the download chip used to be a fixed shortlist — Edit, Rotate, Reverse, Lock, Sanitize, Compress. Now it has a search input at the top and the full OxygenPDF catalog underneath, grouped by category (Organize, Edit, Convert, Security, Optimize). Pick any tool and it opens fullscreen over the chat with your filled PDF already loaded — no re-upload, no losing the conversation. The original quick actions stay at the top for one-tap operations; the catalog is for when you want the full tool experience (page-by-page rotation, watermark options, redaction, etc).

The "Edit in editor" item on the download chip now opens the existing /tools/edit-pdf experience as a fullscreen overlay over the chat instead of navigating away — your conversation stays put underneath. The More menu also picked up three new actions: Rotate 90° (clockwise per click, stacks for 180°/270°), Reverse page order, and Compress (structural). The chip's label and filename track every action you apply, so a fully worked-over PDF reads as e.g. "Filled, rotated, locked, and compressed PDF" — and once an action has been applied, its menu item flips to a "done" state to keep you from doing it twice.

The filled-PDF download chip picked up a "More" ellipsis modeled on the continuation tool's tool-picker. Open it on a filled chip and you get three follow-up actions: Edit drops the file into /edit-pdf via the continuation context (no re-upload), Lock flattens the form so the recipient can't change your answers, and Sanitize strips the PDF's identifying metadata (author, title, producer, timestamps). The chip's label and filename update to reflect what's been applied — "Filled and locked PDF", "Filled, locked, and sanitized PDF" — so the user always sees what they're about to download. Each follow-up action is one Convex action call: load the existing filled PDF, transform with pdf-lib, replace the storage blob, patch the message.

Drop a fillable PDF into chat, hand the assistant the values you want plugged in, and a download chip appears in its reply with the form actually filled. The assistant emits a structured fill-pdf directive alongside its prose answer; the server loads the original PDF, fuzzy-matches each label to a real AcroForm field with pdf-lib, applies the values, and stores the filled document. The bubble shows a pulsing chip while it works, then resolves to a tappable card that downloads the result with a sensible filename. Forms without AcroForm fields, or labels we couldn’t match to anything on the page, surface a quiet warning instead of silently failing.

The chat workspace got a top-to-bottom design pass. The flat all-white canvas became a warm paper-and-ink surface system: the gutter behind the PDF is now a soft cream, the page itself stays paper-white as the protagonist, and the chat panel sits on a slightly raised warm offwhite. AI answers no longer wear a chat-bubble — they read as editorial prose on a Newsreader serif body with a subtle accent rail down the side, and citation chips became small italic footnote numerals instead of bright blue badges. Your messages flip to a deep-teal bubble with a pinched corner so the asymmetry visually says "I asked, the document answered." The sidebar recesses into the canvas, active chats get a left bookmark-ribbon and a raised paper card, and the empty-state hero now opens with an oversized italic "a" behind "Ask the document anything." Composer pill picks up an inset highlight, the send button is a circular deep-teal disc that nudges on hover. Same panes, same shortcuts, very different emotional temperature.

A new top bar sits above the preview and chat panes. A three-way switch flips between PDF only, split view, and chat only — picks stick across reloads. Theme toggle and your account live up there too, alongside a keyboard-shortcuts shortcut. The old "Indexed — ask anything about this PDF" line was replaced with a small "✦ Ready" chip beside the filename, and a thin progress bar shows up only while the document is still indexing.

The left sidebar now has a collapse button (or ⌘B), and the chat thread on the right is draggable — pull the divider to give the PDF more room or the chat more room. Your width sticks across reloads. The "New chat" shortcut moved off ⌘K (which usually means "search" in apps that have it) to ⌘⇧O, matching ChatGPT and Claude.

Drag across text in the preview and a small toolbar appears above it. Tap Explain or Summarize and the selection goes to the AI as a quoted question. Pick a color to highlight the passage, or drop a bookmark to come back to it later. Both stick to the document, and a "Highlights & bookmarks" button at the top of the preview lists everything you have saved — click any entry to jump straight to its page. Right-click still works the same way for keyboard people. Replies from the AI now end with follow-up chips (Explain more, Give an example, Show source, Summarize this) so you can keep going without inventing a new prompt every turn.

Click a citation chip and you used to get the whole chunk, sometimes a multi-paragraph slab full of facts that had nothing to do with the answer. Citations now carry a verbatim quote, and the preview pane lands the highlight on that exact sentence. Two different chips on the same chunk hit two different sentences. When the quote can't be found (paraphrase, image-only PDF), the highlight drops back to the old chunk flash so you still see the right block.

The chat workspace got a refresh. On phones, a tab toggle at the top swaps between the PDF preview and the chat thread, and tapping any citation chip flips you to the PDF so you actually see the source. The composer is a rounded pill with an embedded send button, an auto-growing textarea, and a kbd-hint footer. The empty state now offers four one-tap starter prompts. Recents in the sidebar bucket into Today, Yesterday, This week, This month, and Earlier. Keyboard shortcuts: ⌘K for new chat, ⌘B to toggle the sidebar, / to focus the composer, ? for the full reference. Hit ? anywhere on the page to see them.

The chat workspace now has a left rail with your recent conversations, a one-click way to start a new chat, and a back link to the rest of OxygenPDF — no more URL surgery to switch threads. Hover any user message to edit and resend it, hover the latest assistant reply to regenerate it. Copy lives on every bubble. Both edit and regenerate truncate the thread cleanly at the fork point so the conversation stays coherent.

Selecting a paragraph in the preview was extending the selection up to every paragraph above it. Cause: pdfjs v5's TextLayer doesn't ship the `.endOfContent` anchor element older versions used to, so empty-space clicks (margins, gaps between paragraphs) anchored on the first text span in DOM order — i.e. the top of the page. We now create the anchor ourselves and toggle a `.selecting` class on pointerdown so the anchor expands to cover the whole layer during a drag.

PDF preview pages now have a transparent selectable text layer over the rendered canvas — drag-select like you would on any web page. Right-click on a selection and a small popover pops up with a question input. Type your question, hit Enter, and the selected passage flows into the chat thread as a quoted prefix to your question, so the AI can answer about that exact span.

Citations were flashing a vertical band sized to the chunk's share of the page — better than whole-page, still rough. The preview now matches the chunk's text against pdfjs's extracted text layer and flashes the actual text bbox: the exact paragraph or sentences the AI cited. Falls back to the vertical band if the PDF has no text layer (image-only scans).

The block-citation migration shipped yesterday relied on `createOrReuseIndex` running on re-upload, but the frontend's `findIndexByHash` shortcut was bypassing it for any non-error cached row — so old PDFs kept getting page-level citations instead of upgrading. `findIndexByHash` now returns null for pre-block-level indexes, forcing the upload to flow through the migration path. Re-upload your PDF and you'll get sub-paragraph citation flashes on the next chat.

Citations used to flash the entire cited page when clicked, which was practically useless on dense pages. Each chunk now has its own pdfIndexElement with an approximate vertical-band bbox, so clicking a citation chip flashes the specific paragraph rather than the whole page. The model is told the block id of every chunk in its context (`<!-- block id="3-c-2" page="3" -->`) and cites with `<cite p="3" id="3-c-2"/>`. Existing PDFs auto-upgrade on next re-upload — no double-charge.

Three rendering bugs collapsed into one bad screenshot: assistant messages were dumping raw markdown (literal `**Helga**`), every bare citation chip was getting a unique number even when it pointed at the same page (so you saw chips numbered 1–42 instead of one per page), and all chips were marked as "missing" so clicking did nothing. Now: messages render with markdown formatting, citation chips dedupe by page, and clicking one scrolls + flashes the cited page in the preview. Also told the model to stop stacking five citations on one claim.

Switched the chat model from gpt-4o-mini to Mistral Large for better instruction-following — the model now actually emits the <cite p="N"/> markers the system prompt asks for. For documents up to 50 pages, the entire OCR'd markdown gets stuffed into the prompt instead of vector search, so broad questions like "list all characters" stop missing the long tail. Longer docs use a wider top-20 retrieval (was top-8). Citation chips appear under the answer and clicking one scrolls + flashes the cited page in the preview.

Switched the chat backend from a flaky Replicate proxy of DeepSeek-V3 (which was rejecting our payload at the SiliconFlow upstream) to a direct OpenAI gpt-4o-mini call — same citation-grounded answers, faster, and one fewer API key to manage. Fixed the blank-white PDF preview by making the shared page renderer wake consumers up when the doc finishes loading. Reworked the indexing scan animation into a softer two-layer sweep that doesn't fight the underlying text.

Fixed the blank white preview that hit when the page-dimension load raced the canvas renderer — pages now paint as soon as they're ready. Added a soft cyan scanner-pass animation that sweeps each page while the index is being built, so the wait feels intentional. Cleaned up the redundant per-page "Failed" pill that was just repeating the doc-wide status on every card.

Replaced the per-page vision-OCR loop with a single Mistral OCR call. A 50-page PDF now indexes in ~10–20 seconds instead of ~3 minutes. Chat unlocks the moment the first chunks are embedded — you can start asking questions while the rest of the document is still being processed in the background.

Reload-safe, regenerate-safe, no re-OCR. Upload a PDF once and we index it in the background — content-hashed, so re-uploads of the same file are instant. The chat is now subscription-aware (free tier with monthly cap) and runs entirely on our infrastructure: server-orchestrated DeepSeek-OCR with proper rate-limit retry, OpenAI text-embedding-3-small for chunked retrieval, DeepSeek-V3 over only the relevant chunks. Grounded citations with click-to-source preserved.

Bring your own Replicate token and the chat sidebar gains a cloud mode powered by DeepSeek-OCR + DeepSeek-V3. OCR indexes every page with bounding-box grounding so answers come with citation chips you can click to jump straight to the highlighted region on the source page. Same conversation, same slash commands — but with cited answers and an extensible provider layer so we can swap in Kimi or Claude later without touching the UI.

Drop a file bigger than the free workspace cap and you used to get a dead-end "exceeds 10MB limit" banner. Hard tier blocks now pop an Upgrade to Pro dialog directly, with the cap spelled out and a one-click checkout path.

Edit PDF, Compare, Compress, Redact, Remove Watermark, the PDF→Text/Word/Markdown family, and several shared rendering paths could all throw "No GlobalWorkerOptions.workerSrc specified" if you opened them as your first tool in a session. Every pdfjs entry point now configures its own worker instead of relying on a different code path to do it first.

Deep-dive comparisons for people searching "Sejda alternative" and "Wondershare PDFelement alternative" — what each product actually is in 2026, what their free tiers really do, and where their privacy stories hold up or fall apart.

Edit PDF and PDF Reader now paint pages straight onto a canvas sized to your actual device pixels, so text stays sharp on Retina and at high zoom instead of going through a PNG that the browser had to smooth out.

Every PDF tool now shares the same action bar — workspace, mobile, and desktop. Big accent-colored primary button with a ⌘↵ shortcut, plus a Start over button with ⌘⌫ on standalone pages.

New Rust→WASM engine for smart PDF text extraction with layout analysis. PDF to Word, PDF to Markdown, and PDF to Text now produce significantly better output with proper headings, lists, and structure.

Every tool page now features in-depth articles, FAQs with structured data, and visual diagrams — making it easier to understand each tool and boosting discoverability.

New tool for splitting two-up scanned pages into individual pages. Handles booklets, side-by-side scans, and A3-to-A4 splitting with guided configuration.

Compress PDF now handles huge files (up to ~1 GB). Set a target file size and let the tool auto-optimize, convert to grayscale for line drawings, or use the new Extreme preset.

Streamlined top navigation bar — secondary links collapsed into a compact "More" menu for a cleaner, less cluttered header.

Ask questions about your PDFs using on-device AI. Upload a file and chat — all processing stays local. Slash commands coming soon.

New font system with DM Sans, Fraunces, and IBM Plex Mono for sharper, more consistent typography across all platforms.

The desktop app now checks for and installs updates automatically with a splash screen and status notifications.

Rebuilt desktop app on Electron with native tabbed editing, platform detection, and improved build pipelines.

License validation API, account-based activation, and rate-limited validation endpoints for Pro users.

Pin your favorite tools, filter by category, and browse the full toolkit from a redesigned tools page.

Full annotation toolkit — add text, drawings, stamps, symbols, callouts, and freehand highlights with undo/redo and draft auto-save.

OxygenPDF now runs natively on macOS, Windows, and Linux with tabbed editing, keyboard shortcuts, and drag-and-drop tab reordering.

Chain multiple PDF operations into reusable workflows — build once, run on any file.