What changed,
and when.

1.0.2 24 September 2026

Print opens Windows’ own Print dialog, PDFs open as tabs in one window, and most tools work on a document its author restricted Current

Print opens Windows’ own Print dialog — printer, pages, copies — and prints what the tab shows, unsaved changes included. Ctrl+P opens it too. It used to hand the file to whichever application Windows uses to print PDFs, and on a machine where CreasePoint is that application a second CreasePoint window opened on the same file and nothing printed. The pages are drawn onto the printer by the same separate process that reads the document, so a printer driver that crashes cannot take your unsaved changes with it. A document whose author set it not to be printed is refused and says so; one that allows only low-quality printing prints each page as a picture, which is what that setting asks of a reader. Microsoft Print to PDF and the XPS writer ask where to save first. Windows now knows the program as CreasePoint PDF, the name it has on the Store, rather than Creasepoint — the name the Print dialog and Task Manager showed.

Opening several PDFs from Explorer, or double-clicking one while CreasePoint is open, adds them as tabs in the window you already have and brings it to the front. Each file used to open a window of its own. If the hand-over ever fails, the file opens in a window of its own rather than not at all. Starting CreasePoint from the Start menu or the taskbar while it is open brings that window to the front as well, rather than opening a second one.

Most tools now work on a document that restricts what may be done with it but asks nobody for a password — the bank statements, payslips and government forms that 1.0.1 learned to open. In 1.0.1 they refused it with “Remove its password first”, a step nothing could take: there is no password to remove, and CreasePoint does not lift a restriction without the owner password. Watermark, page numbers, header and footer, crop, stamp, annotate, attachments, fill, edit, redact, recognise text, compare, conversion to Word and to a web page, and taking the pictures out now run on it, in the window and on the command line. The 1.0.1 notes said that the copy you save from such a document does not carry its restriction. Whether it does depends on what you did, so the window now reads back the file it has just written — when you save, extract, split or merge — and tells you. Measured on 2026-09-24: a watermark keeps the restriction exactly as it was, and deleting a page leaves the copy with none — as do reordering, extracting, splitting, merging and inserting pages from another document, which all rebuild the document. The command line says which, once per run. The original is still never written over. Signing, marking where to sign, removing a signature, adding a password, changing the document’s properties, setting bookmarks and removing an annotation still refuse, and each now gives its real reason instead; adding an annotation, or changing its colour, works.

Rotating a page no longer rebuilds the document around it. It used to copy every page into a new document and then put back what the copy had left behind, and not everything came back: measured on 2026-09-24 against 1.0.1, rotating one page of a restricted, tagged report returned it with no restriction and without the tags a screen reader follows. Rotate now turns the page where it is, so the restriction, the tags, the form, the bookmarks, the attachments and the document’s dates are still there, because nothing took them away. Deleting and reordering pages still rebuild — deleting in place leaves the bookmarks pointing at the wrong pages — so they still drop a restricted document’s restriction and a tagged document’s tags.

Redacting part of a page whose whole content is wrapped in one block — which is how some programs export a page — removed everything on that page. The block cannot be taken apart, so the mark took all of it. The window warned that everything inside the block would go, but it listed no lines, reported that no text had been removed, and the check that reads the saved file back had nothing to look for, so it passed. Measured on 2026-09-24 against 1.0.1: a mark over the page number of such a page left none of the page’s 700 characters. The block is now unwrapped into ordinary page content first, so the mark takes the lines under it as it would on any other page, and the same mark leaves 688. The unwrapped page is compared with the original — the same text, the same picture — and is not used if anything moved; then the whole block still goes, but the list names every line it holds before you agree. The window and the command line both work this way. A restricted document’s block cannot be unwrapped at all, so there the whole block still goes, with the same list first. Editing the words on such a page still finds nothing to edit: the unwrapping has reached redaction, and not yet the on-page editor.

On a page printed from a web browser, a large redaction mark — a drag across the full width of about nine lines — painted the whole page black, while the text outside the mark stayed in the file underneath. Such a page sits on one background that covers all of it, the mark touches the background, and the black box grew to cover everything the mark touched. Something that covers most of the page no longer decides how much is painted, so the box covers the mark and the smaller things it touches. The background itself still goes, because the mark touches it, and the list now says so for a mark of any size. On those same pages every letter is stored on its own, and the check that reads the saved file back confirmed only that one copy of each marked letter had gone, rather than every copy that was marked. It counts every copy now.

Redaction, editing the text on a page, and compressing a page’s pictures turned colour gradients solid black or removed them, because the engine that writes the changed page out again cannot write a gradient. Measured on 2026-09-24 against 1.0.1: redacting a heading on a report printed from a browser turned the coloured band across the top of the page black. The gradients are now put back where they were, and the band keeps its colour. When a page’s gradients cannot be put back exactly, the page is left as the engine wrote it and the result says they may be black or missing; compression leaves that page’s pictures as they were instead. A restricted document cannot be repaired this way, so redacting one still loses its gradients, and now says so.

Arabic, Hebrew, Urdu and Persian came out of conversion to Word and to a web page backwards. Each line was rebuilt from the positions of its letters, read left to right, which walks a right-to-left line from its far end. Measured on 2026-09-24: a recognised Hebrew page came out of 1.0.1’s web page export with every word reversed. A line that is mostly right-to-left is now taken in the engine’s own reading order — the order the text export always used, which is why it was right — and a page of right-to-left columns is read from the right-hand column first. A line that mixes a right-to-left sentence with a left-to-right phrase is still given the one direction it has more of.

Recognising text no longer loses the whole document to one page it cannot read. A single damaged page, or one past a safety limit, ended the run, and nothing recognised before it was kept; now that page is left as it was, the rest come back, and the result names the pages that have no text under them. The command line names them as well and exits with 1, so a script hears about it. A run in which no page at all could be recognised still fails, and says why, and so does a run whose reading stops altogether — a page the reader cannot finish within its time limit, or one that crashes it — and nothing from that run is kept. A page too large to recognise at the usual resolution — A1 or larger — stopped the run with advice to choose a lower resolution, which nothing let you do. It is now recognised at the highest resolution that fits, and a page that fitted before is recognised exactly as before.

Saving pages as pictures at a resolution too high for the page wrote white squares and reported success. Measured on 2026-09-24: the 1.0.1 command line, asked for 800 DPI on an ordinary five-page A4 report, wrote five PNGs of 2000 by 2000 white pixels and said it had rendered five pages. It now refuses, writes nothing, and says how large the page would have been. A page that will not draw for a reason of its own is still written as a blank, so the numbering matches the document, but the blank now has the page’s shape rather than a square, and the window and the command line both say how many of the pictures are blanks. In the viewer, a page too large to show at its usual resolution — more than about 7,800 square inches, the size of a plot or a roll banner — was a blank in 1.0.1. It is drawn now, at the highest resolution that fits, which makes it look smaller beside the other pages than it is.

Compression’s advice before it starts counts pictures properly. A logo drawn on every page was counted once for every page, so a document of text with a logo could be told it was mostly pictures and that compressing would help; each picture is counted once now. Pictures on a page wrapped in one block, which is how some programs export a page, were not counted at all, so a document made of them was called mostly text. It is now told that it is mostly pictures compression cannot reach, and to expect a few percent at best. The command line gives both figures.

Thai typed into a watermark, a header or footer, page numbers or text added to a page came out as a row of empty boxes, with nothing in the searchable text, because it was set in Arial, which has no Thai — measured on 2026-09-24 against 1.0.1. It is set in Leelawadee UI now, a Thai face that comes with Windows, and reads back as what was typed. It is still placed one character at a time, without the shaping Thai needs, and the watermark, header and numbering tools still say so.

Recognised Traditional Chinese is searchable. Characters such as 水 and 高 were read correctly and then stored as look-alike radicals from another part of Unicode, because the font the text layer is written in draws both with one shape — the page looked right, and a search for them found nothing. The text layer now stores the character that was read.

The privacy policy says more exactly what can leave your machine: a crash dump is the one route out that you did not choose, and printing to a printer on your network or in the cloud is you sending the pages there, through Windows’ print queue. The About window says the same. The policy also says that it is about the Windows application only, and that the Android application is a different product with a policy of its own.

The privacy policy, the About window and the command line’s claims now name every file you will find if you take up their invitation to read the package’s import tables. They named one, tesseract.dll, and one of its imports, and put that import down to a dependency of the OCR engine. Measured on 2026-09-24, the OCR engine imports ten Windows networking functions — socket, connect, send and recv among them — for Tesseract’s own debugging viewer, which no OCR feature switches on; and two files that come with the .NET runtime import them as well: msquic.dll, its library for HTTP/3, which nothing here asks for, and createdump.exe, its crash-dump helper, which this application does not use. None of those imports is reached by anything this application does, and an import is not a call. The three files are the same ones 1.0.1 carried; only the description was short. The same sentences now begin “Apart from the optional timestamp on a digital signature”, because the program that fetches that timestamp is part of this application, and the sentence has to be true on its own. The security notes give the engine’s path and hash for the arm64 package as well as for x64, so either can be checked.

Settings, under Updates, described an update check that is not running yet as though it were — once a day, from a link on our site that does not exist — and said that nothing is downloaded in the background, which is not true of a copy from the Microsoft Store: the Store downloads a new version in the background, as it does for everything it installs. It now says what the privacy policy says. A plain .msix checks nothing. The update manifest for a direct download is planned and not serving yet; when it is, Windows’ own installer will check it when you start the application, at most once in twenty-four hours, and every eight hours in the background, whether or not the application is running. CreasePoint itself downloads nothing.

The notices that travel in the package say what it holds. NOTICE said that no code of ours uses the .NET networking assemblies; the separate program that fetches the optional signature timestamp does, and NOTICE now says so. The About window’s Licences tab called every component permissive and counted our own README files among the licence texts; it now names the one exception NOTICE records — Adobe’s DNG SDK, built into the Skia graphics library — and counts the licence texts apart from our notes. The security notes said that redaction was not built yet, and spoke of the prebuilt engine this project stopped using as the one in use; they now describe redaction as it ships, with what it cannot reach, and the engine as built from source and pinned by its hash. The FreeType note no longer calls CreasePoint’s own code Apache-2.0; it is under the CreasePoint Licence.

Still wrong, and known: digits typed in Persian and set in Arial are copied and searched as Arabic-Indic digits, which look the same, and a no-break space is copied as an ordinary space. Both come from how the engine names a character that shares its shape with another. Fixing them means writing that name from what was typed, and it is not in this release.

New

• Print, through Windows’ own Print dialog, with Ctrl+P.
• Every PDF opened from Explorer arrives as a tab in the one window.

Fixed

• Most tools work on a document that restricts what may be done with it and asks for no password, and what the saved copy carries is read from the file rather than predicted.
• Rotating a page keeps the document’s restriction, tags, form, bookmarks and attachments.
• Redacting part of a page wrapped in one block takes the lines under the mark rather than the whole page, and lists them.
• A large redaction mark on a browser-printed page no longer paints the whole page black, and the check afterwards counts every marked copy.
• Redaction, text editing and compression keep colour gradients instead of turning them black.
• Right-to-left text comes out of conversion to Word and to a web page in reading order.
• One unreadable page no longer ends text recognition, and a page too large for the usual resolution is recognised at one that fits.
• Saving pages as pictures at too high a resolution refuses instead of writing white squares.
• A page too large for the viewer’s usual resolution is drawn at one that fits rather than left blank.
• Compression’s advice counts each picture once, including pictures drawn inside a block.
• Thai in a watermark, header, page numbers or added text is drawn rather than left as empty boxes.
• Recognised Traditional Chinese stores the characters that were read, not look-alike radicals.

Changed

• The privacy policy says that printing to a network or cloud printer is you sending the pages there.
• The privacy policy, the About window and the command line name all three files whose import tables show networking functions — tesseract.dll, msquic.dll and createdump.exe — and say that an import is not a call.
• The security notes give the engine’s path and hash for the arm64 package as well as for x64.
• Settings, under Updates, says what the privacy policy says, and no longer that nothing is downloaded in the background.
• NOTICE, the security notes and the About window’s Licences tab describe what the package carries: the timestamp program’s use of the networking assemblies, redaction as it ships, the engine as it is built, and the one licence that is not permissive.

Still not right

• Persian digits set in Arial are copied and searched as Arabic-Indic digits, and a no-break space as an ordinary space.
• Deleting or reordering pages still drops a restricted document’s restriction and a tagged document’s tags.
• When a page wrapped in one block cannot be unwrapped exactly, redacting it still removes the whole block, and says so first.
• The on-page text editor cannot yet reach inside a page wrapped in one block.
• Redacting a restricted document still loses its gradients, and says so.
• On a restricted document, redaction and text editing cannot trim the embedded fonts’ character maps afterwards, so they may still name characters the removed text used, and redaction cannot unwrap a page exported as one block, so the whole block goes. Each says so.
• In the window, compressing a restricted document and the batch tools do not yet say whether the copy kept its restriction; saving, extracting, splitting and merging do.

1.0.1 11 September 2026

Protected documents open, scans in six more scripts are searchable, and the page fills the window

A bank statement would not open. If a document carries the kind of protection that restricts what may be done with it — printing allowed, copying and editing not — but asks nobody for a password, CreasePoint opened it as the word “failed” and showed a message about countersigning, which is a feature you had not touched. Bank statements, payslips, card statements and most government forms are shaped exactly that way. They open now. The refusal came from the part of the reader that looks for places to sign, answering a question the window asks about every document without being told to — and a refusal there was never a refusal of the question, it was a refusal of the document.

Saving one of those documents writes a new file rather than replacing the original, and says so first. The restricted file you were given keeps its restriction; the copy you write does not carry it. That rule already existed for documents that ask for a password, and could not apply to these because nothing in the session knew they were protected at all.

Recognised text in Vietnamese, Turkish, Polish, Czech, Romanian and Hungarian is searchable. It was not: the page was read correctly and then every accented character was destroyed on the way into the file, so the scan looked perfect and could not be searched for any word carrying an accent. Arabic, Hebrew, Urdu and Persian went into the text layer backwards, and went unnoticed for the same reason — the page looked right. Twenty-eight of the forty-seven bundled languages are now checked end to end - the page is recognised, the text layer is read back, and the script’s own letters have to be there, rather than merely some characters being there. The nineteen without a test scan are written down by name in the suite rather than left to be assumed.

A document fills the window when you open it instead of sitting small in the middle of it, and it is sharper. Those were one problem: pages were drawn at a fixed resolution that only improved once you zoomed past 100%, so at the size documents actually opened at, the sharpening never ran. A very long page — a statement, a receipt — steps back rather than running four screens tall. Zoom is remembered per document now, so opening one file no longer changes the zoom of another in a different tab.

PDF files show their own icon in Explorer rather than the application’s. A folder of documents was a wall of solid violet squares, because the file type had been pointed at the app’s own tile.

1.0.0 5 September 2026

The first release

CreasePoint does forty-seven things to a PDF, and it does all of them on your machine. There is no account to make, nothing to upload, no page limit, no watermark and no paid tier holding a feature back. It is free, and it stays free, because a copy of it costs us nothing to give you.

The thing worth understanding before anything else is how it treats your file. Open a document and edit it, and nothing is written anywhere until you press Save. The changes are held in memory, the file on disk is untouched, and the banner across the top tells you exactly how many changes are waiting and that the original has not moved. When you do save, you choose whether that replaces the document you opened or writes a copy, and the application says which it is about to do. A password-protected document is never written over at all: what you save from one is always a new file, and the file you opened keeps its password.

Text editing happens on the page rather than in a dialog. Double-click a paragraph and type into it; it re-wraps as you go and Enter puts it down. Signing uses a certificate from the Windows store or a DSC USB token, which is what most people filing anything official in India already have in a drawer. OCR ships with forty-seven languages, Indian ones included, and the language data is inside the installation - it does not fetch anything the first time you use it. Compression can target a size, which is the only thing you want when a portal refuses anything over 300 KB.

Two honest notes. The application is signed by Certum, so Windows can tell you who wrote it before you run it. And redaction removes the content rather than covering it: the objects under the mark come out of the file, and what is drawn afterwards is drawn over an empty space. Before it runs it lists what it is about to take - an image under the mark goes whole, a line of text the mark only clips goes whole, and a form field's value is not in the page at all and will survive. Read that list. It is the part of the feature that matters.

New

• Forty-seven tools in the window and fifty-one on the command line, all of them included.
• Redaction that removes the content rather than covering it. Afterwards the saved file is read back and the removed text counted: if it did not go, the operation fails instead of reporting success. The window and the command line run the same check.
• Editing as a session: nothing reaches disk until you save, with undo, redo and discard across the whole session.
• On-page text editing - double-click a paragraph and type where it sits.
• Digital signing with a Windows certificate or a DSC token, PAdES, with an optional timestamp.
• OCR in forty-seven bundled languages, including Indian ones, with the language data inside the installation.
• Compression that targets a file size, with presets for common portal upload limits.
• Forms filled on the page through the document's own form layer rather than by drawing over it.
• A command line that mirrors the window, for scripting and batches.
• Plain text out of a document, the document as one web page, and pictures in and out: PNG, JPEG, BMP and TIFF both ways, GIF in, and CCITT Group 4 scans read. A multi-page TIFF arrives as pages and leaves as one file.

Still not right

• Redaction does not reach a form field's value, because that value is held in the document's form data rather than on the page. It says so, by field name, before it runs; clear the field or flatten the form first.
• There is no way to cancel a long operation once it starts; it will stop itself if it takes too long.
• Editing text in a font the document only partly embeds re-sets that line in the closest system font, and the application tells you when it has.
• CCITT Group 3 TIFFs - what a fax produces - are refused by name rather than read. Group 4, which is what a document scanner set to black and white produces, reads. Saving a Group 3 file again as anything else is the way through.