What OriginPage supports on Windows 11

OriginPage is a private evidence reader for Windows 11 x64, with a seven-day free trial through Microsoft Store. A one-time purchase is required to continue after the trial.

This page describes the formats, workflows, operating limits, and local-processing boundary of the current v1 product.

Supported environment

OriginPage v1 is designed for:

• 64-bit Windows 11;
• English documents and English OCR;
• local SSD-backed storage; and
• a supported hardware and per-Workspace operating envelope.

The reference performance laptop has an AMD Ryzen 5 5600U, 16 GB of RAM, and SSD storage. That is the machine used for performance targets, not a claim that every 16 GB Windows computer will behave identically.

Supported document formats

The current source and workspace limits are:

Resource	Limit
PDF source file	256 MiB; 1,000 pages
Pages requiring OCR in one PDF	100
TXT source file	32 MiB
DOCX source file	64 MiB
Documents in one workspace	100
Available physical memory before answer generation	At least 4 GiB

These are acceptance limits, not performance promises. Extraction, indexing, and answer latency depend on file structure and the PC. The 16 GB reference configuration above is total installed RAM; the generation check concerns memory available at the time of the request.

PDF

OriginPage accepts an unencrypted PDF when its pinned local pipeline can process selectable text, locally recognized pages, or a combination of both.

Image-only or scanned pages are not automatically trusted. They enter OCR Review, where every page requiring recognition must be approved or excluded before the Document can become Ready. Approved OCR text can contribute to the text used for search and evidence; pending or excluded OCR text cannot.

PDFs that are encrypted, malformed, empty, over the defined limits, or cannot be processed safely are rejected rather than partially published as Ready.

TXT

OriginPage supports plain-text files that meet its encoding, content, and size rules. Empty, binary-like, malformed, or over-limit files are rejected with an explicit outcome.

DOCX

OriginPage supports unencrypted, macro-free .docx files whose visible WordprocessingML text can be processed by its local extraction pipeline.

The initial contract does not include:

• legacy .doc files;
• macro-enabled .docm files;
• Word templates;
• encrypted or password-protected Word documents;
• comments or deleted revision text;
• embedded-object contents; or
• claims that a Word passage has a stable rendered page number.

Supporting .docx text is not the same as reproducing Microsoft Word’s complete visual layout.

The practical guide to searching multiple Word documents with AI offline shows how these boundaries affect headings, lists, footnotes, tables, search modes, and source verification.

Inspecting what became evidence

An imported Source File becomes a managed Document inside one Workspace. OriginPage never modifies or deletes the user-owned Source File and does not depend on it after the managed copy is accepted.

The product retains a deterministic text representation for inspection, persistence, evidence offsets, and prompt passages. That lets users review what the system extracted instead of assuming that an “indexed” status means every relevant page was understood correctly.

Removing a Document deletes OriginPage’s managed copy and processed data without touching the original Source File.

Multiple isolated Workspaces

OriginPage supports multiple named Workspaces. Each Workspace is a separate local storage and retrieval boundary containing its own Documents and durable Conversations. One Workspace is active at a time, and the app restores the active Workspace after restart.

This replaces the outdated single-Workspace description that appeared in the first version of this article.

The Personal Workspace is created on first launch and acts as the default. Creating or switching Workspaces does not merge their Documents, searches, or answer evidence.

Multiple durable Conversations

A Workspace can contain multiple named Conversations. Creating a new Conversation does not erase existing ones. One is active at a time, and completed questions, answers, scopes, claims, and sources are designed to survive restart.

Conversation history can help interpret a context-dependent follow-up, but it is not treated as independent factual evidence. Earlier OriginPage answers do not become sources for later answers.

Direct Search without generation

OriginPage includes non-generative Direct Search across Ready Documents in the active Workspace:

• Hybrid combines semantic and lexical retrieval;
• Exact phrase looks for the requested wording;
• Keyword emphasizes lexical matches; and
• Semantic looks for related meaning.

Direct Search returns inspectable passages and does not add a generated turn to a Conversation. It is intended for cases where finding a clause, date, name, or passage is more useful than asking a model to write an answer.

Grounded answers with explicit scope

Before asking a question, the user chooses its Question Scope: all Ready Documents or an explicit non-empty selection. That eligible set is preserved with the question and does not change later if Documents are added or removed.

OriginPage retrieves bounded passages from that scope and supplies them as the answer’s sole factual material. Accepted factual Claims link to exact retained evidence spans that can be opened in the source inspector. The answer contract is designed to keep conflicting evidence visible and to say when eligible evidence cannot support the requested answer.

For a worked example, read A citation is not enough.

Local-only processing boundary

Document extraction, reviewed OCR, indexing, Direct Search, persistence, and answer generation are designed to run on the current Windows device. During ordinary work, the OriginPage App, Core, and Inference process tree makes no network connection and has no cloud-model fallback.

That claim does not include Windows or Microsoft Store services outside the OriginPage process tree, and it is not a claim that the PC is invulnerable to administrators or other sufficiently privileged software. The local-processing guide and privacy page explain the boundary in more detail.

What Ready and supported do not promise

Ready means the document completed the ingestion workflow. It does not certify perfect reading order, complete table interpretation, or error-free OCR. Inspect the parts that matter for the question. Selected documents define eligibility; retrieval may use only a subset of their passages. A supported format is not a guarantee that every feature of every file in that format becomes evidence.

Workspaces organize application storage and retrieval. They are not separate Windows accounts or security sandboxes, and removing a managed copy does not securely erase external backups or the independent original.

Explicit v1 boundaries

OriginPage v1 is not intended to provide:

• cloud synchronization or collaboration;
• mobile, browser, or macOS access;
• user-selected models, providers, or API keys;
• agents, web search, plug-ins, or a local API server;
• PDF editing, signing, forms, or conversion;
• general image understanding beyond reviewed PDF OCR;
• legacy Office-format support; or
• unlimited Documents, content, conversation history, storage, or memory use.

Those constraints keep the first release focused on one measurable job: searching selected local Documents and inspecting the evidence behind an answer.

Current release status

As of August 26, 2026:

• OriginPage is publicly available for Windows 11 x64 from Microsoft Store;
• the app includes the multi-Workspace, multi-Conversation, PDF/TXT/DOCX, OCR Review, Direct Search, Question Scope, and claim-linked evidence workflows described above; and
• Microsoft Store supplies the signed installation and future Store updates.

Method note: This capability page was updated after the first Microsoft Store release was approved. It describes the shipping v1 contract; the in-app About & privacy statement and Store listing are the current references for the installed release.