Meshgrove

---

Contents

• Why Meshgrove?
• Features at a glance
• Screenshots
• Installation
• Getting started
• User guide
  • Browsing the gallery
  • The 3D viewer and its tools
  • The details panel
  • Library, search and filters
  • Tags and notes
  • Favourites, collections and print lists
  • The print log
  • G-code files
  • Readmes and text files
  • Printers and the bed check
  • Printability check
  • The inbox
  • Duplicate finder
  • AI assistant and MCP (optional)
  • Plugins (optional)
  • Working with your slicer and other apps
  • Archives (ZIP, 7z, RAR, TAR)
  • Moving files to the trash
  • Backups, export and import
  • Thumbnails in Dolphin and file dialogs (Linux)
• Keyboard and mouse reference
• Supported file types
• Settings and files on disk
• Privacy and safety
• Performance
• Platform support
• Troubleshooting and FAQ
• Building from source
• Architecture
• Development
• Roadmap
• Contributing
• Tip jar
• Credits
• License

Why Meshgrove?

Anyone who prints a lot ends up with folders full of files called Body1.stl, final_v3_fixed.3mf and pack.zip. A normal file manager shows a generic icon for each of them, so you open model after model in the slicer just to find the right one.

Meshgrove shows those folders as a gallery with a rendered preview of every model. That includes the models inside ZIP/7z/RAR packs and the plate pictures your slicer stored in 3MF projects. It also gives you what a model collection needs: an instant search across the whole library, tags and notes, favourites, collections and print lists, a log of what you printed, a duplicate finder, a print-bed check, and a one-click hand-over to your slicer.

What makes it different from other model managers:

• Your folders stay as they are. Meshgrove browses and indexes files where they are and never rearranges them on its own; it works fine on read-only drives. Importing from a downloads folder and placing files by tag are opt-in, shown to you before they happen, journalled and undoable.
• Native and fast. It is written in Rust and renders with the GPU (Vulkan, Metal or DirectX 12 through wgpu). There is no Electron, no web view and no server. Thousands of files and models with millions of triangles stay fluid.
• Free and open source under the GPL, with no account, subscription or telemetry.
• Made for real libraries on spinning hard drives. Reads are scheduled so visible tiles come first, and everything else is cached.

This is the beginning of the README. Read the rest at the original. Read the full README ↗