What OriginPage supports at launch
A clear guide to supported document formats, Workspace behavior, and the boundaries of the first Windows release.
OriginPage is intentionally specific about the documents it can process. Clear limits make failures understandable and keep quality measurable.
Supported files
The first release supports:
- PDF files with usable, selectable Unicode text
- TXT files containing supported plain text
- DOCX files that are unencrypted and macro-free
Scanned or image-only PDFs require optical character recognition and are not supported yet. Legacy .doc files, macro-enabled .docm files, encrypted Word documents, templates, and embedded-object contents are also outside the initial format contract.
One Workspace, one Conversation
OriginPage opens into a single local Workspace. Imported Documents remain available independently of the Source Files they came from, and the current Conversation is restored when the app opens.
Starting a new Conversation clears the transcript while leaving Documents in place. Removing a Document deletes OriginPage’s managed copy and processed data, never the original Source File.
Built for bounded, reliable work
The first release sets operational limits for Document count, total content, conversation length, memory readiness, and local storage. These are not arbitrary restrictions: they define the range in which answer quality and performance can be measured consistently.
As OriginPage grows, those boundaries can expand—but they should always remain explicit.