Track what you print, what it cost, and what it took. — www.3dprintlog.com
3D Print Log is a free, open-source print journal for 3D printing. Log a print straight from your slicer, and it records the settings, filament used, print time, and cost — so you can look up how you printed something six months ago instead of guessing.
| Repository | What it is | Stack | License |
|---|---|---|---|
| 3d-print-log-ui | The web app at 3dprintlog.com | Angular / TypeScript | AGPL-3.0 |
| 3d-print-log-api | REST API backing the site and every integration | ASP.NET Core / C# | AGPL-3.0 |
| 3d-print-log-app | Android app shell | Cordova / JavaScript | AGPL-3.0 |
| Slic3rPostProcessingUploader | Post-processing script for PrusaSlicer, OrcaSlicer, Bambu Studio, and Slic3r | C# | MIT |
| 3d-print-log-cura-plugin | Cura plugin — send a print to your log from the slicer | Python | MIT |
The two slicer integrations are MIT so they can be freely bundled and adapted; the app and API are AGPL-3.0.
You do not need to run any of this to use 3D Print Log — just sign up. These repositories are here if you want to contribute, self-host, or write an integration for a slicer we do not support yet.
- Using it: documentation
- Contributing: each repository has a
CONTRIBUTING.md; the web app and API include full local setup instructions - Found a bug? Open an issue on the repository it belongs to. If a slicer is reporting a value incorrectly, that is usually the plugin rather than the API — attaching the G-code header helps enormously
Issues labeled good first issue are scoped to be self-contained and are a reasonable place to start. The parser code in the slicer plugins is the most approachable part of the codebase: each slicer writes its own G-code comment format, the parsers are small, and they have clear test seams.
Please report vulnerabilities privately to hello@3dprintlog.com rather than in a public issue. See the security policy.