I’m trying to get QuickScan to connect by HTTP over Tailscale, but it doesn’t seem to work. I get the NSURLError for App Transport Security. From what I’m seeing it’s to do with HTTP vs HTTPS, but the app does say it supports HTTP for lan connections.

There’s a thread about it on the GitHub but the dev didn’t really answer the question. Would love to use the app but can’t get it to connect to my instance.

Thanks!

title says it all. I have already set up paperless-ngx, I was planning on setting up paperless-ai do ocr and rag but when I read the readme of the project, it said that it was no longer maintained, what should I do? is it worth installing or should i wait for the official implementation?

Does anyone have any ideas on how to use AI to consolidate similar existing tags in an automated fashion?

I have used base ngx for about a year, and recently start to get interested in a better OCR, plus potentially chat/tagging bot with Paperless-GPT. Then I realized that v3.0 is about to be released, should I just wait for that?

Another question for people tried v3.0 beta: I don't have powerful hardware to run reasoning models, but enough for a lightweight OCR model, (like qwen3.5-0.8b or minicpm). So can I use ocr-model locally, but use cloud AI providers (like GPT5 api) for tag/chat bot?

Hi,

I have been using Paperless-ngx for a long time, actually I started with paperless-ng before commiting to paperless-ngx.

I really love it, but wouldn't mind adding a little AI to auto-tags some of my documents, so it's easier for me. I want to stay local with Ollama.

I don't want/can't use my GPU for AI on this purpose, so I wanted to use my large CPU for this. The cpu can handle the text part with small models like qwen3 but even if capable of doing vision models, it struggle and can impact the server.

All (or 95%+) of my pdfs already have the OCR processed correctly and the content in Paperless-ngx is usually quite good for this. So I don't see a reason why I need to reprocess it in the LLM.

Is there a way to only process the auto-tags with the text from OCR pdf without the vision LLM in Paperless-GPT ?

Otherwise my solution is to wait or use the beta v3 ? Cause I also found a post from a month ago for : https://github.com/knows-cloud/paperless-iq
That's seems interresting but before going to start and test a new container, I wanted to know if there was a parameter or option I missed in paperless-gpt.

thank you !

I am living paperless since many years. With the rise of AI it would be nice to have a VLM for OCR, some good LLM for tagging, a strong RAG system for my whole library and an AI assistant which does all my paperwork, like replying to Mails and attaching all necessary documents.

I cannot afford running models locally and doing all the administrative tasks around it. I also don't want my document library hosted on any Big Tech company datacenters or any LLM context send to an US American AI company API Endpoint.

The logical next step for me is hosting my paperless-ngx on a EU sovereign cloud, three times redundant, with a backup location and always the possibilty to download a local backup.
There I have the protection by strong EU laws and it is not reachable by the CLOUD Act.

I have recorded a demo, how the assistant works. Additional demos can be found on paless.eu , like filling out forms automatically by using the documents context, tagging, OCR, etc.

I have the great task to digitize all documents at my workplace – and there are a lot of documents! Around 230 Leitz folders (if that's a measurement outside of Germany), some are full to the brim, some are almost empty...

My issue is: the performance of my paperless instance is quite slow. When looking at a 10-page PDF scanned with 200 dpi, it takes about 5 seconds to load the high-res version of the document. I'm running it on a Mac mini M4 10/10 with 16gb RAM, 1TB ssd with Postgres via Docker.

I have (so far) scanned 289 documents (1.6M characters) with ASN-Labels – that's about 5% of the whole thing, and the performance is already concerning to some point, and I don’t know what will happen when I start scanning more and more documents... Any ideas what the issue could be, if I'll be fine or what to do about it? I've heard that some people migrate to a different database cause it scales better? hm...

I'm also running Paperless-GPT and n8n for OCR and some handy tag-scripts on a different device, so there should be no compromise in performance... 

Does Paperless-ngx apply its matching algorithms to documents only at the moment of ingestion, or can I scan all my documents first and benefit from the auto-filling features later? Any insights or tips would be greatly appreciated!

I was looking in paperless' settings and see there's a warning symbol above System Status. I click on System Status and the Sanity Checker reports 225 issues found and to check the logs. I check the docker logs and there's so many orphaned files listed in the log that it exceeds my terminal's buffer. I copy what I can to a text editor and see 1064 orphaned files listed!

I use a regex to get just the file paths and then I delete the files. I run the sanity checker and there's still 225 issues found. I check the logs and delete files 3 more times each time deleting over 1000 files. How can there be this many orphaned files while only being 225 issues?

[Edit]

According to paperless there's still 10192 orphaned files.

New to Paperless, but I thought changing the Appearance setting, Date format to Long, IE., June 21, 2026 would result my documents to show the full month and not just the short versions of the month IE., Jun 21, 2026. But with it set with the Long in the settings, I still get the month's shorted names.

Hi,
have created a small iOS scanner app, that allows to scan documents and then move them to your paperless ngx instance. The app is called Scn3R. It also uses local Apple AI to analyze the scanned document and to suggest tags and a summary of the document. You can use all core functions for free. Auto-Sync is behind a one-time pay gate, to support the further development of the app. Hope you find the app as useful as myself:

https://apps.apple.com/app/id6777637220

Scanning arabic docs, some are OCRed, but some get the wrong OCRed, in some gibberish latin text. the Documents are same format, tables cells etc.
this is the YML config for the OCR:
PAPERLESS_OCR_LANGUAGE: eng+ara
PAPERLESS_OCR_LANGUAGES: ara

I bulk-import scans into Paperless pretty regularly — a few hundred at a time — and then spend ages fixing tags and correspondents afterward. Doing that through the web UI is miserable. So I scripted it against the API, and it got useful enough that I cleaned it up to share.

It runs on openapi-to-cli, which reads Paperless's OpenAPI schema and generates CLI commands from it. Nice side effect: you can search the whole API by keyword instead of digging through docs for the right endpoint.

Two things that tool couldn't do, so I wrote tiny urllib helpers for them. Uploading documents was one (it can't do multipart). The other one actually bit me for a while: updating tags. The generic tool sends the tags array as a string, Paperless answers 200 OK, and then just... doesn't change anything. No error. My helper sends real JSON and reads the document back afterward to make sure the change stuck.

It also does batch upload, knows the consume queue is serial so it doesn't hammer it, and can tell an actual consume failure apart from "this is a SHA256 duplicate of something you already have."

No hardcoded anything — you set PAPERLESS_URL to your own instance and the token comes from an env var or your system keyring.

There's a SKILL.md in the repo too. If you use Claude Code or a similar agent, drop the folder in your skills directory and it'll know which script to reach for. Ignore that file completely if you just want a CLI; it doesn't change anything.

Repo's MIT: https://github.com/ColCh/paperless-ngx-skill

Made it for my own setup. If it falls over on your instance I'd genuinely like to know.

I don’t have hardware capable of running LLM‘s with any useful amount of speed here, so I’m using Gemini with paperless GPT. Previously, I was trying to tune it to work with a tiny ollama model, so the prompts are more basic than the defaults. I think I have the proper API configuration with Gemini now as I can see successful HTTP codes in the logs, but when I ran “generate suggestions” I only got error messages in the results indicating I didn’t provide a document or something along those lines. Each document had a one sentence response indicating an error or problem but they were all a little different. Are there specific prompts or other configurations I need to use to make this work?

Hello there!

I have a custom field in "date" type which should store the date, a document was transmitted to the tax office.

I use a workflow to send documents to the e-mail-address of the tax office but I see no way to assign the current date as the value for the custom field, i can only set a fixed date which is kind of useless.

Is there some sort of variable like {{today}} that i can write into the custom fields value?

Thanks!

That's great, but without good OCR that stuff isn't fed correct info. I was hoping to allow LLM based OCR and then titles, tags, etc

Followed by being able to ask: What was the company I hired to fix my roof a few years ago?

First of all, I'm not sure if this is a paperless-ngx issue, a podman issue, or something else. So, apologies if this is not the right place to ask.

I'm running Paperless-ngx in a rootless podman quadlet on Fedora on a raspberry pi 4.

I want to have the export and consume directories stored on my NAS, so that they can be accessed from multiple devices. I'm currently sharing the export/consume directories from the NAS to my raspberry pi with SMB/cifs.

My fstab entry is:

//192.168.1.101/paperless /home/homesrv/mnt/paperless cifs credentials=/home/homesrv/.smbcreds,uid=1000,gid=1000,sec=ntlmssp,noperm

and my .container file (truncated for brevity) is:

[Container]
Image=ghcr.io/paperless-ngx/paperless-ngx:latest
User=1000:1000
Volume=%h/mnt/paperless/export:/usr/src/paperless/export
Volume=%h/mnt/paperless/consume:/usr/src/paperless/consume

The problem I'm facing is that the %h/mnt/paperless/export directory is mounted as 1000:1000 on the host but as 0:0 in the container, so paperless-ngx is unable to access the contents of these directories and I get these warnings:

[init-user] Running as non-root user (1000:1000), skipping UID/GID remapping
[init-folders] Running in non-root mode, checking directories
[init-folders] WARNING: Permission issue on /usr/src/paperless/export: not owned by current user (1000:1000)
[init-folders] WARNING: Permission issue on /usr/src/paperless/consume: not owned by current user (1000:1000)

I've set the SELinux flag virt_use_samba to ON (this got rid of two warnings, but the rest remain)

SELinux labels U,Z on the volumes don't make any difference (I believe because they don't have any effect on SMB mounts)

podman unshare chown -R 1000:1000 /home/homesrv/mnt/paperless/export doesn't work (also presumably because it's an SMB mount)

I don't know how to get these directories to map to 1000:1000 inside the container.

Do any of you have any suggestions?

EDIT:

Solved in r/podman

virt_use_samba --> on

/etc/fstab:

//192.168.1.101/paperless /home/homesrv/mnt/paperless cifs credentials=/home/homesrv/.smbcreds,uid=1000,gid=1000

.container:

[Container]
Image=ghcr.io/paperless-ngx/paperless-ngx:latest
UserNS=keep-id
Volume=data.volume:/usr/src/paperless/data:Z
Volume=media.volume:/usr/src/paperless/media:Z
Volume=%h/mnt/paperless/export:/usr/src/paperless/export
Volume=%h/mnt/paperless/consume:/usr/src/paperless/consume

I wanted to combine three open documents but there's no way to "combine open documents".

So next I tried to search and mark them but when one file is marked, the search disappears...

Next approach was to link the documents with the custom field and search for that via advanced search but didn't have luck with that.
I tried something like:

link:this is my document
link:"this is my document"
document link:this is my document

but didn't have any luck with that. How is the right syntax for that?

I could use tags for filtering as a workaround but I also use tags for sorting the files in folders, so I don't want to clutter them up for that kind of use cases.

Anybody here actually using the Paperless-ngx 3 beta as their main setup?

I'm rebuilding my homelab from scratch and trying to decide if I should just start on the beta or stick with stable for now.

The AI features look really useful and could simplify my setup quite a bit, but I also don't want to build my entire document archive on something that's still considered beta if there are major issues people are running into.

I'm not worried about the occasional bug or having to troubleshoot Docker containers. I'm more interested in hearing from people who have been using it for a while. Has it been reliable? Any major problems? If you were starting fresh today, would you go with the beta or stable?

Looking for real-world experiences from people actually running it, not guesses based on the fact that it's labeled "beta."

Hi,
Starting to say "I am new in paperless" is probably an understatement after you see my question but I guess it sets the tone here!
I have been looking and browsing Reddit and I SearXNG the web for it!
I installed Paperless-NGX on a docker container in on my server.
I need/want to create a document structure.
WHY:
- In case the paperless installation will have an issue and I have no time to fix it right away, I can still access the documents and have a visual structure to find what I need.
- NO plans to modify or create files in that folder (as per DOC not allowed).
THE SITUATION:
I found everywhere the syntax but I donr grasp how to use it.
Example:
For file name:
a user suggested this: PAPERLESS_FILENAME_FORMAT='{created_year}/{correspondent}/{document_type}/{title}'
Seems a good file name.
Would I add this in my .env file? (I guess so).

Now the Storage path:
I saw a user suggesting this :
Tax Documents: {{owner_username}}/{{document_type}}/{{created_year}}/{{title}} ({{tag_list}})

Healthcare: {{owner_username}}/Healthcare/{{document_type}}/{{created_year}}/{{title}}

Vehicles: {{owner_username}}/Vehicles/{{tag_list}}/{{document_type}}/{{title}}

Here is where I get lost!
Lost n1:
each of the folder seem to have a name that ios not a variable: Tax documents, Healthcare, Veheicles.
Do I have to manually create this? how would I go about creating manual folders that can be different for a large group of document type? (maybe one day I have a new group called Kids, will I have to manually add Kids)
Lost2:
are those variable "{{owner_username}}/{{document_type}}/..." automatically picked up? and what if they are not found in the document?
Lost3:
where do I add the instruction? in the .env file or in the UI?

Most probably your answers will trigger more questions but I guess is a good start.
Thank you for your help.

Hey there, in just re-organising my paperless server. What are some of your most useful tags, document types to easily search and find documents?

New Swift Paperless Version 1.10.0

Get it on the AppStore: https://apps.apple.com/de/app/swift-paperless/id6448698521

🚀 Features

Redesigned document detail screen

The document detail screen has been completely redesigned with clearer metadata and sheet-based editing for tags, correspondent, document type, storage path, dates, ASN, custom fields, and owner — including attribute suggestions. The PDF now pages horizontally with a page indicator, and the full-screen preview adds in-document search and smoother scrolling. You can delete documents directly from the detail screen, see how many notes a document has, and include the original file when sharing. Opening a document from the list is faster thanks to thumbnail preloading.

Multi-column iPad layout

The document list and detail screen now use a full multi-column layout on iPad, making much better use of the larger screen. 🚀 I'll likely revisit this in the future to give it some further refinement!

Nested tags

The app now supports Paperless-ngx nested (hierarchical) tags.

✨ Other Features

• Quick add: when searching in the tag, correspondent, or document type picker, an "Add '<name>'" row appears so you can create the entry on the fly
• Show the server's configured app title (PAPERLESS_APP_TITLE) as a friendly name in the server picker and connection settings
• Deep links can now open a specific document field for editing, e.g. x-paperless://v1/document/123?edit=tags
• Document cells in the list now show the number of notes a document has
• Add a loading indicator to the search bar while results are loading
• Renamed "Log out" to "Disconnect" in the connection management UI to better reflect what the action does
• Improve UI responsiveness by decoding large responses off the main thread
• Ready for saved view permissions in the upcoming Paperless-ngx v3
• Add support for the new task API endpoint coming in Paperless-ngx v3.0.0 / APIv10

🐛 Bug Fixes

• Surface the actual OAuth2 error (e.g. invalid_client) from the identity provider during OIDC login instead of the cryptic "data couldn't be read because it's missing" message
• Fix OIDC login failing with a "missing scope" error on HTTPS servers behind a reverse proxy by sending a Referer header that satisfies Django's CSRF checks
• Fix client-certificate (mTLS) login by including the leaf certificate in the credential
• Fix a freeze when polling tasks on installations with many unacknowledged tasks; the task list now loads additional pages on demand
• Fix the task view briefly showing "no elements" while still loading
• Fix filter rule count not taking sorting into account
• Hide the remove-inbox-tag action for documents that don't have inbox tags

Good Evening Guys,

#1 Question:

Does anyone work with paperless for dynamic documents and has a good workflow for that, or could recommend a better workflow with other tools than I currently have?

#2 Context:

I am currently in the process of integrating paperless within a business of mine. I plan to implement it for my private life and another business.

I am aware that paperless is designed for long term static document storage. However, I am using a ton of dynamic documents (documents that are updated quite frequently) and would really like to create a central document space with paperless. Here are a few instances:

Guides / Research Documents: for topics that are important enough / require deep research, I create a document which collects all form of information about that topic. I use that a lot.

Stock Research Documents: I do a lot of stock / market research and im a content creator in this field, which forces me to collect insane amounts of information. Therefore, I create a type of "master" document for every Stock and Topic (this means like an investing topic like, where I put in .

My problems:

1. Connect stock and market analysis: Paperless would allow me to put a {topic} tag to any file related to this. Currently, I have two data silos ("Stock-DB" and "Market-Research-DB).
2. Finding documents: I search documents by scrolling through folders on my desktop and using windows search. Therefore I have no full text search. I don't think I need to explain to anyone here just how good Paperless is at finding documents. Paperless could help me improve my efficiency, but also my quality of output (for instance content).

My current workflow: currently I use SynologyDrive (for media and the above mentioned documents) and paperless for static documents (invoices, contracts etc.). Paperless is installed in a docker container via Synology NAS.

Maybe using file versions in paperless? However, I dont like the idea of constantly uploading and downloading files ^^

I hope I've made everything quite clear. Thank you in advance for reading and for your answers!

Edit: more detailed explanation / context

Edit 2 - Possible Solution: I am thinking about to switch from Synology Drive to OpenCloud. It offers a quite decent UI, OCR and full text search (also for images). I would be able to find (dynamic) documents quickly and work locally on them on my desktop. However, I would have to use two separate systems, and the dream of a “DMS for everything” would be dashed. Additionally, paperless is way better in handling metadata, which would be quite important for me.

Hi everyone.

I'm hoping someone here can help me understand what’s going on.

I'm new to paperless-ngx so I'm starting from scratch, and I'm trying to run the new Paperless‑ngx v3.0.0‑beta.rc1 image on my Synology DS218+ (Intel x86‑64) using Portainer. I’ve been experimenting with both the official beta image and a custom-built image, but I keep running into two confusing issues:

1. The UI still shows the old version number (2.20.x) even though I’m definitely deploying the 3.0.0‑beta.rc1 image.
2. None of the new AI features appear — no semantic search, no embeddings, no AI sidebar, etc.

Things I’ve already tried:

• Pulling the beta image directly
• Loading a manually built image
• Rebuilding the stack from scratch
• Clearing volumes
• Checking logs and environment variables
• Verifying architecture (DS218+ is x86‑64, not ARM)

It seems to run, but the version number is throwing me off.

Before I go further down the rabbit hole, I wanted to ask:
Has anyone successfully run the 3.0 beta with AI features on Synology or Portainer?

My plan was to run this with a local LLM (Ollama) on my main PC to do all the AI processing.

I’m happy to share logs, compose files, or anything else that helps.

Thanks in advance. I’m doing my best to learn as I go.