Keep a Print Log

A print log is your fastest way to stop guessing. By writing down the exact printer, filament, slicer profile, and the single change you tested (plus what you observed on the first layer and the final part), you can reliably repeat successes and diagnose failures later.

TL;DR

Log the slicer profile name, filament, temps, bed prep, and the one change you tested; then write what you saw on the first layer and how the print ended. If it isn’t written down, you’ll waste time repeating the same “mystery” failures.

Keep a Print LogTopic-specific diagram for the concept, checks, and tradeoffs in this lesson.Baselineprofile, filament, tempsBed prepclean + adhesion methodFirst layerstick, gaps, line widthOutcomesuccess or fail layerOne changesingle variable next runArchivesave profile with log
A simple workflow diagram helps learners follow the habit: record baseline, observe first layer, record outcome, choose a single next change, and archive settings with the log entry.

Why a print log matters (in real life)

Most print problems aren’t random: one variable changed and you didn’t notice (new spool, different bed cleaning, enclosure door open, different profile). A short log turns printing into a controlled experiment so you can (1) repeat a good result and (2) trace a failure to a specific change instead of making a pile of unrelated tweaks.

What to log (minimum to reproduce)

  • Part name and file version (or link/path)
  • Date/time and printer name
  • Filament: brand, material, color, and spool ID or label (if you have one)
  • Nozzle size and layer height
  • Nozzle temperature and bed temperature
  • Slicer profile/preset name plus any overrides (speed, retraction, cooling)
  • Bed prep: cleaned with what, adhesion method (none/glue/tape), enclosure on/off
  • Outcome: success or the exact failure point (for example: “detached at layer 20”)

One-minute log template (copy/paste)

  • Part/file:
  • Printer:
  • Filament (material/brand/color/spool):
  • Nozzle / layer height:
  • Temps (nozzle/bed):
  • Profile + overrides:
  • Bed prep + enclosure:
  • First-layer notes:
  • Final result (time, defects, failure layer if any):
  • Next test (one change):

What to watch and write during the first 3 minutes

  • Adhesion: are lines sticking or curling at the edges?
  • Line width: consistent “squish” or gaps between lines?
  • Extruder behavior: clicking, grinding, or under-extrusion signs
  • Bed and nozzle cleanliness: any blobs dragging through lines
  • Environment: draft from a fan/AC, enclosure door open, unusual room temperature

Fast workflow for your next print

  1. Pick a low-risk test (small calibration part or a short version of the real part).
  2. Before you hit print, write the baseline: profile name, filament, temps, and bed prep.
  3. Watch the first layer and note what you see (don’t rely on memory).
  4. After the print, write the outcome and one clear next action (for example: “increase bed temp by 5 C” or “reduce speed 10%”).
  5. Save the project file or export the slicer profile using the same name as the log entry so settings and notes stay paired.

When logging would have saved you

A print failed and you can’t reproduce the issue

Likely cause: No record of what changed between runs (profile, temps, filament, bed prep)

Fix: Start logging: filament, temps, profile name, bed prep, and the single change tested

A great print happened once but not again

Likely cause: A hidden variable changed (different spool, bed cleaning method, enclosure/door, room temperature)

Fix: Add spool ID/label plus bed prep notes (cleaner used and adhesion method) to every entry

You’re stuck making random tweaks with no improvement

Likely cause: Multiple settings changed per attempt, so results are ambiguous

Fix: Pick one parameter to test and keep everything else constant for 2–3 runs