Edit your PDFs in chat
Attach a PDF to a chat and ask for changes in plain words. Portail can now replace text, delete, rotate and reorder pages, pull out a few pages into a new file, merge in another PDF, stamp a watermark, add page numbers, add a line of text anywhere on a page, and fill in form fields. You get the edited copy as a normal download card, and your original upload is never touched. Because the copy is a new file, you can keep going in the same chat: ask for another change and Portail edits the version it just made. Edits are checked step by step. If a piece of text can't be found, for example because the page is a scan, Portail tells you which step failed instead of pretending it worked. One honest caveat: replaced text is drawn over the old text in a standard font, so fonts and colors can differ from the original, and covering text this way is not a secure redaction, since the hidden text can still be selected in the file. Portail says so whenever you ask it to hide something sensitive.
577 words
Ask for changes to an attached PDF: replace text, delete, rotate or reorder pages, merge PDFs, add a watermark or page numbers, fill forms.
The edited PDF arrives as a download card, and your original is never modified.
Follow-up edits work on the version Portail just made, and any step that fails is reported honestly.
Portail v2.6.25 shipped on 2026-10-13 as a patch release focused on edit your pdfs in chat. Attach a PDF to a chat and ask for changes in plain words. Portail can now replace text, delete, rotate and reorder pages, pull out a few pages into a new file, merge in another PDF, stamp a watermark, add page numbers, add a line of text anywhere on a page, and fill in form fields. You get the edited copy as a normal download card, and your original upload is never touched. Because the copy is a new file, you can keep going in the same chat: ask for another change and Portail edits the version it just made. Edits are checked step by step. If a piece of text can't be found, for example because the page is a scan, Portail tells you which step failed instead of pretending it worked. One honest caveat: replaced text is drawn over the old text in a standard font, so fonts and colors can differ from the original, and covering text this way is not a secure redaction, since the hidden text can still be selected in the file. Portail says so whenever you ask it to hide something sensitive. The work is recorded here because small releases are still product history. They change how people sign in, read responses, pay for access, share conversations, open files, or trust the system when something goes wrong.
The main changes were direct: ask for changes to an attached pdf: replace text, delete, rotate or reorder pages, merge pdfs, add a watermark or page numbers, fill forms, the edited pdf arrives as a download card, and your original is never modified, and follow-up edits work on the version portail just made, and any step that fails is reported honestly. That list is intentionally plain. It names what changed without turning the release into theatre. When a release fixes a build, a redirect, a storage path, or a UI edge case, the value is often that users stop noticing the problem. The archive keeps that invisible work visible enough for future debugging and for anyone checking whether Portail has cared about the details over time.
This version also fits into the wider Portail contract. One account, one chat history, and one model picker only work if the smaller pieces keep their promises. Authentication has to fail clearly. Billing has to count honestly. Uploads have to arrive in a form models can read. Admin tools have to show the operator what happened instead of hiding it behind a blank screen. v2.6.25 moved that contract forward in its own narrow lane.
The screenshots attached to this entry show the public release record as it now appears on portail.cc. For older releases, this archive was rebuilt from the git history, package version changes, release modal text, and commit subjects. That means the page is honest about its source: it documents the shipped change and preserves the record going forward, even when the exact old production screen cannot be recreated from a single saved image.
The practical result is simple. Someone landing on this page can see the version number, date, release tier, headline, highlights, and a real rendered screenshot of the archive page. Search engines can index the post through the canonical URL, sitemap entry, and structured data. Future releases now have a standard to meet before deploy, so the history should get cleaner from here instead of fuzzier.