Folders and Files

As a user, you might occasionally want to see where a specific file is stored. Sometimes it's simple curiosity, other times you may want to inspect logs, review saved settings, or work directly with the files for troubleshooting or development.

And since LumiFind is privacy-focused software, everything is kept transparent so you can always see what is on your computer and why it is there.

Application Logs (system locations)

While running, LumiFind writes background logs with names following the pattern lf.YYYYMMDD_HHMM_XXX.log. Depending on how LumiFind was installed, these are stored at:

Operating System	Location	Comment
Windows	%LocalAppData%\MIDILLI Tech\LumiFind\Logs\	Only exists if installed for the current user.
Windows	C:\Program Files\MIDILLI Tech\LumiFind\Logs\	Only exists if installed for all users.
macOS / Linux	~/.lumifind/logs/	Auto-saved session logs appear here when enabled (see below).

The .lumifind Folder

Operating System	Path
Windows	C:\Users\%username%\.lumifind
macOS / Linux	~/.lumifind

This is the default folder for settings, license files, analysis metadata and analysis contents.

Tip: Settings → Open Settings Folder opens this directory directly.

Files and folders inside .lumifind

File / Folder	Purpose	Comment
settings.json	Contains user settings for LumiFind.	Can be edited manually, but with care! See Settings File.
license.json	Contains device- and user-bound license information.	If deleted or tampered with, the license cannot be activated again. Licenses must be released only using the License Manager.
search_history.json	Lists the last performed search queries.	If you are using console mode, history will not be kept.
lumifind_db.sqlite3	Database keeping track of analyzed files and their metadata. Usually small in size.	Default location may vary between installation types (directly under .lumifind, or inside the index folder). Its path can be changed via the db_file setting in settings.json.
lumifind_db/	Folder holding the actual analysis data for documents, images, voice and videos. May grow as the number of analyzed files increases.	Location can be changed via the index_folder setting in settings.json.
thumbnails/	Smaller versions of the analyzed images, used both for detecting changes and displaying them in the interface. Follows the same folder structure as the indexed content.	Can be relocated via the thumbnail_folder setting.
models/	Cached copies of downloaded AI models (embedding, transcription and detection models).	Can be relocated via the models_folder setting.
<model_name>.pt	Object detection model weights downloaded on demand for frame analysis.	Stored at the root of .lumifind; safe to delete, they will be re-downloaded when needed.
manifest.json	Cached update information used by the built-in updater.	Refreshed automatically when checking for updates.
logs/	Folder storing important information and error logs in the event of a problem.	If you enable Settings → Auto Save Logs, session logs also appear here after each run.

Inside the Index Folder (lumifind_db)

Besides your analysis data, LumiFind keeps small marker files here:

File	Purpose
.lumifind_indexing.lock	Temporary marker while an indexing operation is running, preventing concurrent index writes.
.lumifind_readonly	Marker indicating the index is currently read-only (e.g. during maintenance or after an interrupted operation).

Note: Do not delete marker or database files manually while LumiFind is running. If an indexing operation was interrupted unexpectedly, remove the lock markers only after making sure no LumiFind process is active.