HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
NanoNets
docext
Python2025–2025
NanoNets / docext

docext

An on-premises, OCR-free unstructured data extraction, markdown conversion and benchmarking toolkit. (https://idp-leaderboard.org/)

4Distinct people
6Mentions
0Explicit recommenders
2.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

An on-premises, OCR-free unstructured data extraction, markdown conversion and benchmarking toolkit. (https://idp-leaderboard.org/)

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week6 dated mentions

Observed mentions: 2025-04-08 10:46:42 UTC to 2025-06-16 10:53:48 UTC. Weeks start Monday, UTC.

01232025-04-07 00:00:00 UTC to 2025-04-14 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 commentsApr 72025-04-14 00:00:00 UTC to 2025-04-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-21 00:00:00 UTC to 2025-04-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-28 00:00:00 UTC to 2025-05-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-05-05 00:00:00 UTC to 2025-05-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-05-12 00:00:00 UTC to 2025-05-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMay 122025-05-19 00:00:00 UTC to 2025-05-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-05-26 00:00:00 UTC to 2025-06-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-02 00:00:00 UTC to 2025-06-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-09 00:00:00 UTC to 2025-06-16 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2025-06-16 00:00:00 UTC to 2025-06-23 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 commentsJun 16

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Apr 72025-04-07 00:00:00 UTC2025-04-14 00:00:00 UTC220
Apr 142025-04-14 00:00:00 UTC2025-04-21 00:00:00 UTC000
Apr 212025-04-21 00:00:00 UTC2025-04-28 00:00:00 UTC000
Apr 282025-04-28 00:00:00 UTC2025-05-05 00:00:00 UTC000
May 52025-05-05 00:00:00 UTC2025-05-12 00:00:00 UTC000
May 122025-05-12 00:00:00 UTC2025-05-19 00:00:00 UTC000
May 192025-05-19 00:00:00 UTC2025-05-26 00:00:00 UTC000
May 262025-05-26 00:00:00 UTC2025-06-02 00:00:00 UTC000
Jun 22025-06-02 00:00:00 UTC2025-06-09 00:00:00 UTC000
Jun 92025-06-09 00:00:00 UTC2025-06-16 00:00:00 UTC110
Jun 162025-06-16 00:00:00 UTC2025-06-23 00:00:00 UTC303

What Hacker News says

6 sources
Hey, the reason for the long processing time is that lots of people are using it, and with probably larger documents. I tested your file locally seems to be working correctly. https://ibb.co/C36RRjYs Regarding the token limit, it depends on the text. We are using the qwen-2.5-vl tokenizer in case you are interested in reading about it. You can run it very easily in a Colab notebook. This should be faster than the demo https://github.com/NanoNets/docext/blob/main/PDF2MD_README.m... There are incorrect words in the extraction, so I would suggest you to wait for the handwritten text model's release.
In Nanonets-OCR-s – OCR model that transforms documents into structured markdown
Full disclaimer: I work at Nanonets Excited to share Nanonets-OCR-s, a powerful and lightweight (3B) VLM model that converts documents into clean, structured Markdown. This model is trained to understand document structure and content context (like tables, equations, images, plots, watermarks, checkboxes, etc.). Key Features: LaTeX Equation Recognition Converts inline and block-level math into properly formatted LaTeX, distinguishing between $...$ and $$...$$. Image Descriptions for LLMs Describes embedded images using structured <img> tags. Handles logos, charts, plots, and so on. Signature Detection & Isolation Finds and tags signatures in scanned documents, outputting them in <signature> blocks. Watermark Extraction Extracts watermark text and stores it within <watermark> tag for traceability. Smart Checkbox & Radio Button Handling Con
Read the rest
verts checkboxes to Unicode symbols like , , and for reliable parsing in downstream apps. Complex Table Extraction Handles multi-row/column tables, preserving structure and outputting both Markdown and HTML formats. Huggingface / GitHub / Try it out: https://huggingface.co/nanonets/Nanonets-OCR-s Try it with Docext in Colab: https://github.com/NanoNets/docext/blob/main/PDF2MD_README.m...
In Nanonets-OCR-s – OCR model that transforms documents into structured markdown

Show HN: Open-source 3B param model better than Mistral OCR

Excited to share Nanonets-OCR-s, a powerful and lightweight (3B) VLM model that converts documents into clean, structured Markdown. This model is trained to understand document structure and content context (like tables, equations, images, plots, watermarks, checkboxes, etc.). Key Features: LaTeX Equation Recognition Converts inline and block-level math into properly formatted LaTeX, distinguishing between $...$ and $$...$$. Image Descriptions for LLMs Describes embedded images using structured <img> tags. Handles logos, charts, plots, and so on. Signature Detection & Isolation Finds and tags signatures in scanned documents, outputting them in <signature> blocks. Watermark Extraction Extracts watermark text and stores it within <watermark> tag for traceability. Smart Checkbox & Radio Button Handling Converts checkboxes to Unicode symbols
Read the rest
like , , and for reliable parsing in downstream apps. Complex Table Extraction Handles multi-row/column tables, preserving structure and outputting both Markdown and HTML formats. Huggingface / GitHub / Try it out: https://huggingface.co/nanonets/Nanonets-OCR-s Try it with Docext in Colab: https://github.com/NanoNets/docext/blob/main/PDF2MD_README.m...
9 points · Open discussion
prithiv10·Apr 11, 2025Submission

Show HN: Open-source, cross platform document data extraction with no OCR

The traditional pipeline for unstructured data extraction typically follows these steps: 1. Image → OCR Model (e.g., Google Vision) → Layout Model (e.g. Surya) → LLM → Final Answer However, this can be streamlined using a Vision-Language Model (VLM): 2. Image → VLM → Final Answer Recently VLMs have improved a lot for OCR and document understanding tasks, specifically the Qwen-2.5-VL series. We can run the Qwen-2.5-VL-7B-AWQ model locally with just 16GB VRAM, and perform end-to-end information extraction (fields and table extraction) without any external models. Hallucination with VLMs One question I am asked often is, higher hallucination with VLMs compared to OCR model. This is a valid point. But, even with correct OCR and Layout formatting, LLM can still hallucinate, and can give incorrect final answers. Layout models often struggle wit
Read the rest
h complex documents (e.g., tables, complex sparse document). If the formatted text from the layout model is incorrect the LLM model will always produce incorrect extraction with high confidence. Check out our GitHub repo for implementation details: GitHub: https://github.com/NanoNets/docext
2 points · Open discussion
souvik3333·Apr 8, 2025Submission

Show HN: onprem unstructured data extraction with 4 lines of code

The traditional pipeline for unstructured data extraction typically follows these steps: 1. Image → OCR Model (e.g., Google Vision) → Layout Model (e.g. Surya) → LLM → Final Answer However, this can be streamlined using a Vision-Language Model (VLM): 2. Image → VLM → Final Answer Recently VLMs have improved a lot for OCR and document understanding tasks, specifically the Qwen-2.5-VL series. We can run the Qwen-2.5-VL-7B-AWQ model locally with just 16GB VRAM, and perform end-to-end information extraction (fields and table extraction) without any external models. Hallucination with VLMs One question I am asked often is hallucination with VLMs compared to OCR model. This is a valid point. But, even with correct OCR and Layout formatting, LLM can still hallucinate, and can give incorrect final answers. Layout models often struggle with comple
Read the rest
x documents (e.g., tables, complex sparse document). If the formatted text from the layout model is incorrect the LLM model will always produce incorrect extraction with high confidence. Check out our GitHub repo for implementation details: GitHub: https://github.com/NanoNets/docext Would love to hear suggestions for improvement!
8 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.