स्थानीय दस्तावेज़ एआई

Extract document data using local AI with Ollama

के साथ शुरू

स्रोत दस्तावेज़

डायनामाइट डॉक्स

इसके लिए काम करें

Your local Ollama route

Your local Ollama route · overviewSource document. Model inference on your own computer.. Document type: invoice, statement, form or report. Suggested schema: Named columns inferred from the file. Rows: Structured records for review Illustrative diagram, not extracted customer data.स्रोतस्रोत दस्तावेज़Document typeinvoice, statement, form o…Suggested schemaNamed columns inferred fro…पंक्तियोंStructured records for…समीक्षा हेतु आउटपुटYour local Ollama routeवेब कार्यक्षेत्रहस्ताक्षरित लूपबैक कनेक्शनस्थानीय ओलामा मॉडलआपके कंप्यूटर पर अनुमान लगानाModel inference on your own computer.

उदाहरण स्रोत

स्रोत दस्तावेज़

Document type
invoice, statement, form or report
Suggested schema
Named columns inferred from the file
पंक्तियों
Structured records for review

Model inference on your own computer.

स्थानीय ओलामा
Model inference on your own computer. Illustrative workflow.

Use local Ollama document extraction to turn PDFs, scans and images into fields and tables. Review the source, correct uncertain values and export Excel, CSV or JSON.

Ollama document parsing combines a local model with a workflow that prepares the source and organizes the response. Dynamite Docs uses embedded PDF text when available and a compatible vision model for scanned PDFs, photos and screenshots. The result contains fields and table rows you can check beside the original.

The Dynamite Docs Windows companion connects your browser workspace to local Ollama. Local inference sends document bytes from your browser to a service bound to loopback on your workstation. The companion prepares the request for Ollama and returns a validated extraction without calling an external model API. Use browser-only file storage when the source file should stay on your computer.

Local LLM support is available on Starter, Pro and Scale. Model inference runs on your hardware, while authentication, token issuance, account state and workspace services remain hosted.

Set up local extraction. Local Ollama requires Starter, Pro or Scale, a running companion, and a compatible vision model.

What runs where

  • Browser workspace: Starts the extraction and displays the editable result.
  • Signed local companion: Accepts authenticated requests on loopback port 8756.
  • Ollama: Runs the selected local model through its OpenAI-compatible API.
  • Hosted account service: Issues short-lived tokens and keeps plan and workspace state.

Extract PDF and image data to JSON with Ollama

Extracting PDFs and images to JSON with Ollama requires consistent field names and complete rows. The companion validates the response shape before returning it to the workspace. Check the values against the source, then export the reviewed data as JSON, Excel or CSV.

  • Document type: invoice, statement, form or report
  • Suggested schema: Named columns inferred from the file
  • Rows: Structured records for review
  • Metadata: Document-level context and fields
  • Confidence: Result and field-level review signals
  • Source content: Prepared document context for comparison

फ़ाइल से लेकर समीक्षित परिणाम तक

  1. 1. Install Ollama and a vision model. For PDF and image OCR, choose a model that supports document images, can return structured fields and fits your hardware. Test a scan and a table before relying on it for recurring work.
  2. 2. Install the Windows companion. Install DynamiteDocs from Microsoft Store and launch the companion. Open the web workspace in your browser. The companion listens on loopback port 8756 and Ollama defaults to 11434. Download the Windows companion
  3. 3. Connect from AI Settings. The hosted service issues a short-lived signed token and discovers models available through Ollama.
  4. 4. Extract a PDF or image and review the result. Import the source in the browser workspace and run extraction with the local model selected. The companion prepares the document, calls Ollama and returns the result. Compare identifiers, amounts and table rows with the source before exporting.

Select local models in the same AI panel

The workspace lists the chosen local model alongside hosted and own-key options. Local-only routing can prevent a document from falling back to an external provider.

डायनामाइट डॉक्स लाइब्रेरी का वास्तविक आयात मेनू, जिसमें अपलोड और गूगल ड्राइव के विकल्प शामिल हैं।
वास्तविक एआई प्रोसेसिंग डायलॉग बॉक्स, जिसमें खोज योग्य मॉडल सूची और प्रदाता फ़िल्टर दिखाए गए हैं।
टेक्स्ट एडिटर में निकाले गए टेक्स्ट के बगल में एक खरीद आदेश।
टेबल एडिटर में संरचित विवरण के साथ एक खरीद आदेश।
टेबल एडिटर में निकाले गए लाइन आइटम के बगल में एक खरीद आदेश।
टेबल एडिटर के टोटल टैब के बगल में एक परचेज़ ऑर्डर है, जिसमें टैक्स और अंतिम टोटल दिखाया गया है।
निकाले गए दस्तावेज़ फ़ील्ड और विश्वास संकेतकों के साथ-साथ खरीद आदेश का पाठ।
फ़ाइल का प्रारूप, दायरा, फ़ाइल का नाम और फ़ोल्डर विकल्प सहित Google ड्राइव में निर्यात करने का वास्तविक संवाद बॉक्स।
Dynamite Docs routing rules showing local-only and sensitive-document model policies
The real routing rules panel used to restrict model selection.

The request stays on a short local path

The companion only listens on loopback by default. Every route requires a valid token, and browser origins are restricted to the official app, configured origins and local development.

कदमEndpointपरिणाम
1. TokenHosted /api/local/tokenShort-lived signed local token
2. ModelsCompanion /v1/modelsOllama models available on the machine
3. ExtractCompanion /v1/extractValidated schema, rows and confidence
4. ReviewBrowser workspaceEditable extraction and export choices

Local does not mean effortless or identical

आत्मविश्वास

The workspace still shows confidence and [editable results](/docs/reviewing-extractions-in-data-studio). Review money, identifiers and low-quality scans as you would with any provider.

शुद्धता

Local model quality varies by model, quantization, document type and hardware. A smaller model may be faster but miss dense tables or small text.

विफलता की स्थिति

Extraction stops when Ollama is not running, the model is missing, the signed token expires, the companion cannot be reached or the model returns an invalid result.

उत्पाद सीमा

The companion has a 150 MB upload limit, a default 120-second timeout and batches scanned PDF images within the model image limit. Hardware still sets practical speed and page limits.

Local and BYOK solve different problems

Use local inference when model calls should run on the machine. Use BYOK when an external provider account should be selected and billed directly.

OptionModel runsPlan access
की मेजबानीDynamite Docs selected providerFree, Starter, Pro and Scale
स्थानीय ओलामाUser computer through the companionStarter, Pro and Scale
BYOKExternal provider account chosen by userEvery plan

The processing boundary is specific

Document bytes used for local inference move from the browser to the loopback companion and then to Ollama on the same machine. The companion does not expose an unauthenticated public extraction endpoint.

Account, plan, workspace and token issuance still use the hosted Dynamite Docs service. Teams that need a fully self-hosted application should not treat the local companion as that product.

Questions about local document ai

Which plans include local Ollama?

Starter, Pro and Scale include the local companion. Free does not. This entitlement is separate from BYOK.

Can I use Ollama for offline document extraction?

वेब वर्कस्पेस, साइन-इन और खाता सेवाओं के लिए इंटरनेट एक्सेस आवश्यक है। ओलामा मॉडल इन्फरेंस आपके पीसी पर स्थानीय रूप से चलता है। ओलामा और अपने चुने हुए मॉडल को अलग-अलग डाउनलोड करें।

How do I sign in for local extraction?

अपने ब्राउज़र में डायनामाइट डॉक्स में साइन इन करें। यदि आप किसी योग्य प्लान पर हैं, तो एआई सेटिंग्स खोलें और ओलामा मॉडल चुनने के लिए स्थानीय साथी को कनेक्ट करें।

What is the best Ollama model for document extraction?

Choose a vision model that fits your hardware and returns the required structured response. Compare candidate models on the same scans, small text and multi-page tables. Measure missing fields, row completeness and correction time rather than choosing from a single OCR example.

How do I run Ollama OCR locally on Windows?

Install Ollama and a compatible vision model, then launch the Windows companion. On Starter, Pro or Scale, sign in to the web workspace, connect the companion in AI Settings and select the local model. Import a PDF or image, run extraction and check the result beside the source.

Can Ollama convert a PDF or image to Markdown?

Ollama PDF to Markdown conversion generally requires rendering scanned pages as images for a suitable vision model. Image to Markdown conversion also depends on model output. The Dynamite Docs companion returns structured extraction data. For selectable PDF text, use the separate local PDF to Markdown converter, which runs in the browser without Ollama.

How should I prepare batch PDF extraction or batch image OCR with Ollama?

Test representative files first, including the weakest scan and longest table. Keep a consistent schema, record the expected pages and rows, and review failed or incomplete results separately. The companion processes scanned PDF pages in image batches within its request limit. That page batching is separate from stored multi-file jobs; check the processing route before assuming a job uses local inference.

Where can I find an Ollama OCR Python tutorial or API integration example?

The official Ollama vision API guide includes Python and REST examples for sending images to a vision model. A PDF workflow also needs text extraction or page rendering and output validation. Dynamite Docs connects through the Windows companion without a Python script. Its authenticated local routes are separate from the hosted REST API.

Can I use DeepSeek OCR with Ollama on Windows?

The DeepSeek OCR model page documents image OCR and Markdown prompts. Follow the Ollama Windows setup guide to run a local model. Test its response against the companion extraction contract before choosing it for Dynamite Docs. Text or Markdown output alone does not establish compatibility with the structured fields and rows expected by the companion.

Can I run document extraction locally with Ollama without exposing data to external APIs?

The model-inference request stays on the local loopback path between the browser, companion and Ollama. Account, token and workspace services remain hosted, so review the full storage and retention path before treating the workflow as self-hosted.

अगला दस्तावेज़ कार्य चुनें

संबंधित वर्कफ़्लो

Set up local extraction or compare processing, storage and integration limits.

के साथ शुरू

स्रोत दस्तावेज़

डायनामाइट डॉक्स

इसके लिए काम करें

Your local Ollama route

Your local Ollama route · workflowSource document. Install Ollama and a model → Install the Windows companion → Connect from AI Settings → Extract and review locally. Illustrative diagram, not extracted customer data.स्रोत दस्तावेज़1Install Ollama and a model2Install the Windows companion3Connect from AI Settings4Extract and review locallyप्रत्येक चरण में दस्तावेज़ और परिणाम आपस में जुड़े रहते हैं।
  1. 01Install Ollama and a model
  2. 02Install the Windows companion
  3. 03Connect from AI Settings
  4. 04Extract and review locally
स्थानीय ओलामा
Install Ollama and a model → Install the Windows companion → Connect from AI Settings → Extract and review locally Illustrative workflow.

के साथ शुरू

स्रोत दस्तावेज़

डायनामाइट डॉक्स

इसके लिए काम करें

Your local Ollama route

Your local Ollama route · fieldsSource document. Document type: invoice, statement, form or report. Suggested schema: Named columns inferred from the file. Rows: Structured records for review. Illustrative diagram, not extracted customer data.स्रोतस्रोत दस्तावेज़Document typeinvoice, statement, form o…Suggested schemaNamed columns inferred fro…पंक्तियोंStructured records for…Document typeinvoice, statement, form or reportSuggested schemaNamed columns inferred from thefileपंक्तियोंStructured records for reviewModel inference on your own computer.

उदाहरण स्रोत

स्रोत दस्तावेज़

Document type
invoice, statement, form or report
Suggested schema
Named columns inferred from the file
पंक्तियों
Structured records for review

Model inference on your own computer.

स्थानीय ओलामा
Document type: invoice, statement, form or report. Suggested schema: Named columns inferred from the file. Rows: Structured records for review Illustrative workflow.
डायनामाइट दस्तावेज़ लोड हो रहे हैं... इस पेज को लोड होने में उम्मीद से ज़्यादा समय लग रहा है। कृपया पेज को पुनः लोड करें ।