pdfFactory creates PDF files by acting as a Windows printer. Any application that can print can send its output to the pdfFactory driver, even when that application has no Export to PDF command. The driver renders the pages, then opens a preview where the user can inspect the pending document before saving or sending it. This workflow captures the printed appearance. It does not preserve the source application’s formulas, revision history or editable layout objects.
Print into PDF
The process begins inside the source application. The user opens Print, selects pdfFactory and chooses the pages, paper size and orientation there. Those print settings affect what reaches the PDF session. A spreadsheet whose columns are clipped in print preview will remain clipped after it enters pdfFactory.
Fonts and graphics also pass through the application’s print system and the driver. If the application substitutes a missing font or rasterizes a drawing, the PDF records that rendered result. Checking a few lines at high zoom can reveal substituted symbols, changed spacing or an image that became too soft.
One active session
With its preview window open, pdfFactory can collect several print jobs into one pending PDF. A user can print a cover page from one application and supporting pages from another, then save them together. The jobs arrive in the order they were printed, so sending them out of sequence creates rearrangement work.
The collection behavior changes when the display is hidden. In unattended mode, incoming jobs can be saved as separate PDFs unless a separate collection rule has been configured. Someone expecting one combined file may therefore receive a folder of individual outputs. pdfFactory treats the visibility and automation settings as operational choices rather than cosmetic preferences.
Review the pages
The preview is the point to remove an unwanted page, check orientation and decide whether all jobs belong together. Individual preview pages can be saved separately when only part of the collected material is needed. A physical print can also be started from this stage.
Page removal changes only the pending output, not the original document. That separation is useful, but it can hide a source mistake: deleting a blank page in every PDF is repeated cleanup if the blank page comes from a wrong section break in the source. Correcting the original prevents the next print job from recreating it.
Email stops at handoff
The Send action creates a message through the configured desktop mail client and attaches the generated PDF. Depending on that client’s settings, the message may open for review or wait in an Outbox. pdfFactory completing the handoff does not prove that the mail server accepted or delivered it.
Large PDFs can also exceed an account’s attachment limit. Compressing images may reduce the file, but aggressive compression can make small text in scans unreadable. A shared download link may be the more predictable route for a long document, provided its access permissions match the intended recipients.
Security has limits
Security controls can restrict opening or editing a generated file, depending on the selected edition and settings. A forgotten open password can also lock the owner out. Permissions inside a PDF are not a substitute for controlling where the file is stored or who receives it.
Before deleting the source, open the saved PDF in a different viewer and check the first page, a page with graphics and the final page. Confirm searchable text where search matters. pdfFactory can make a consistent printable record, but that record is only as complete as the pages and print settings sent to its virtual printer.
