The guide and practice files are free to read and download. The complete program is in the paid download; the free practice pack does not include it.
Product details and paid download · Online illustrated guide

Buy and extract the VelesFold ZIP, then open its VelesFold folder. Open app/index.html in desktop Google Chrome. Follow the illustrated example below before buying; the program runs from your purchased local copy.
In your open local copy, follow the controls described below. The four steps are Source batch, Number region, Rule and names, and Review and export.
In Source batch, click Choose PDF or drop a text PDF on the page. VelesFold shows the file name and page count.
In Invoice number region, drag a rectangle over the invoice number on the page preview, or type Left (x) %, Top (y) %, Width % and Height %. Text found in the region on this page shows what was read; use ← Previous and Next → to check other pages.
Under “A new invoice starts when…”, keep The number in the region changes, or choose The page contains a marker text, The page matches a regular expression, or Every page is its own document. Number pattern (optional) and File name template (placeholders {number}, {index}, {pageStart}, {pageEnd}, {pageCount}, {source}) control the names; the preview shows the result.
Under Review boundaries, check that each document starts and ends on the right pages and has the right name.
Click Split and download ZIP (N files). The ZIP contains one PDF per invoice plus VelesFold-manifest.txt and VelesFold-manifest.json, which list the source pages in each file. Your source PDF is not modified.
examples/velesfold/fictional-invoice-batch.pdf: 5 pages from a fictional candle shop, with INV-3101 (2 pages), INV-3102 (1 page) and INV-3103 (2 pages). The invoice number is printed on its own in the top-right corner.
The review shows “3 invoices from 5 pages”: Pages 1–2 → INV-3101.pdf, Page 3 → INV-3102.pdf, Pages 4–5 → INV-3103.pdf. The browser downloads fictional-invoice-batch-split.zip with INV-3101.pdf (2 pages), INV-3102.pdf (1 page), INV-3103.pdf (2 pages), VelesFold-manifest.txt and VelesFold-manifest.json. The status confirms “Your source file was not modified.”
You can correct each invoice number and its page boundaries in Step 4. Changing a number changes its output filename; it does not rewrite the text inside the invoice PDF.
Reset manual changes now asks before discarding your edits. Choose Keep manual changes (or press Escape while the confirmation has focus) to keep working. Reset all manual changes restores the current rule's detected boundaries and names. This cannot be undone; review the resulting plan before exporting. Closing the file or browser still discards this unsaved session.

Worked check: with the paid bundle’s samples/system-a-two-page-invoices.pdf (this six-page sample is not in the free pack), draw around the number at the upper right, leave number-change selected and rename Invoice 1 to CLIENT-APPROVED-001. Open Reset, choose Keep, then export. Expected: CLIENT-APPROVED-001.pdf contains original pages 1–2 with the original A-1001 text; A-1002.pdf contains pages 3–4 and A-1003.pdf pages 5–6. Renaming is not invoice-content editing.
This revision was checked in headless Chrome 152 on Linux, including a 390 px layout. This is not iPhone, other browser, real-accounting-system or physical download acceptance. The existing provisional limits and other compatibility gates remain unchanged.
Draw the rectangle in the Invoice number region step first; the number rule reads that region.
VelesFold has no OCR, so scanned or image-only pages are flagged, never guessed. Use a PDF exported directly from your billing system.
Draw the rectangle tightly around the number only, add a Number pattern (optional), or switch to The page contains a marker text.
Encrypted, password-protected, digitally signed and damaged PDFs are rejected. Batches over 200 pages or 50 MB need your explicit confirmation.
Use desktop Chrome, Edge or Brave version 119 or newer.
Updated 15 October 2026. Examples are fictional or synthetic. Previously obtained software copies retain their included license rights.