Checked against the current Windows build. Where an article names a menu, a button or a message, that is the wording in the application, not a paraphrase.
The keys the window actually binds
Ctrl+S saves over the document you opened. Ctrl+Shift+S writes a copy and leaves the original alone. Ctrl+Z undoes, and Ctrl+Y or Ctrl+Shift+Z redoes. Ctrl+plus and Ctrl+minus zoom, Ctrl+0 returns to 100 per cent, and Ctrl with the wheel does what it does everywhere else.
All of them are handled on the window's own pass before any control sees the key, which is deliberate: somebody who has been typing into a form field and presses Ctrl+S means save the document, not whatever a text box would otherwise have done with it.
That is the list. There is no Ctrl+F — the find box sits at the top right of the ribbon, reads Find in document, and searches when you press Enter. Pages are selected by clicking the number on a page, shift-clicking another for a range, with Select all and Clear in the panel beside whichever tool is about to act on them.
What the command line is, and what it is not
Run creasepoint with no arguments and it prints every command it has, with the flags each one takes. creasepoint --version prints the build. creasepoint engine names the PDF engine and the worker process that loaded it — a separate process, because the command-line program does not load a PDF engine any more than the window does. creasepoint claims prints what this build will and will not claim about where your documents go, which is the same text as the website and ships in the package so the two cannot drift apart.
Every command that produces a file takes --out, and refuses to run without it rather than guessing a name for you. Page lists are one-based and take ranges: --pages 1,3,5-7. Attachments and signatures are numbered from one as well, in the listings and in the flags, because everything else the application says to you counts from one.
The commands, grouped by what you want from them
To look without changing anything: info, info-meta, fields, bookmarks, attachments, annotations, objects, paragraphs, find, signatures, verify, portals and certs.
To change which pages there are: merge, split, extract, reorder, delete, rotate, crop and blank.
To produce something other than the same PDF: compress, ocr, topng, frompics, todocx, images and compare.
To mark up or complete a page: watermark, number, header, annotate, fill, edit, reflow and set-meta.
And for the security work: protect, unlock, sign, unsign and signed-version. That is the whole surface. Nothing is held back for a paid edition, because there is not one.
Passing a password without leaving it in your history
Give --password with no value after it and you are asked for it at the terminal, and what you type is not echoed. Written out in full on the command line it goes two places you did not intend: your shell's history file, which PowerShell writes to disk line by line as you type, and the process list, where any program running as you can read it for as long as the command runs.
That is ordinary behaviour for a command-line tool and a poor fit for this one, so the flag has a form that leaks neither. It applies to any flag whose name ends in password, --pfx-password included. When input is redirected there is no console to turn the echo off on, so a password arriving down a pipe is read as an ordinary line — which is how a script supplies one, and is the case a prompt would otherwise break.
A folder at a time
Inside the window, Batch runs one of six prepared jobs over every PDF in a folder, each file in its own worker: compress to under 300 KB, OCR in English, add page numbers, stamp DRAFT, export the text as Word, flatten the form fields. That covers a lot of Friday afternoons. What it will not do is vary the settings per file, hit a size band rather than a ceiling, or recognise a language other than English.
For those, a loop:
Get-ChildItem *.pdf | ForEach-Object { creasepoint compress $_.FullName --portal neet-ug-certificate --out ./out/$($_.Name) }
Read what each run prints. It reports what it did and anything it could not do, and those lines are the only place a partial failure shows up. Check them before you tell anybody the folder is finished.
The two places worth looking next.
Read the matching guide if you want the reasoning rather than the fix, and check limitations before spending any longer on it — some of what people look for here is absent on purpose.