Skip to content
Discussion options

You must be logged in to vote

There’s no way to fully disable the file size limit in Trilium. Setting TRILIUM_NO_UPLOAD_LIMIT=1 removes the built-in 250MB application limit, but you’ll still hit a hard cap around 400–410MB due to how Node.js and the V8 engine handle large files in memory. This is a technical constraint: Trilium loads the entire file into memory as a string or buffer, and the underlying platform has a maximum size it can handle—errors like “The bound string, buffer, or bigint is too big” come from these limits, not Trilium itself. This cap isn’t related to the database backend and can’t be bypassed by configuration or environment variables. Trilium isn’t designed for large file storage, so for anythin…

Replies: 6 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by eliandoran
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants
Converted from issue

This discussion was converted from issue #4718 on October 14, 2025 19:11.