← All articles

Exporting a Feeding Diary as PDF: What Actually Needs to Be in the File

At some point your feeding diary stops being just for you. A pediatrician asks what the last few weeks looked like. A specialist wants something in writing before an appointment. Your partner's parents are taking the baby for a weekend and want a copy of what's been recorded so far. In all three cases, the answer is usually the same: a PDF.

PDF is the boring, unglamorous format that works everywhere — it opens on a hospital desktop from 2014, it prints the same way it looks on screen, and nobody needs your app, your account, or your phone to read it. That's the whole appeal. But an export is only as useful as the thinking you put into it before you hit the button.

Why PDF and not a screenshot

Most parents' first instinct is screenshots. Fifteen of them, sent as a burst in a messaging app. It technically transmits the information and it's terrible for everyone involved.

A PDF beats a screenshot roll for three practical reasons:

If you keep your diary on paper, the equivalent step is photographing or scanning the pages into a single PDF — most phone camera apps and free scanner tools do this. Same logic: one file, in order, readable.

Pick the date range before you pick anything else

The most common export mistake is exporting everything. Six months of entries is a forty-page document that nobody will read closely, which means the three days that actually matter get buried.

Ask yourself what question the file is supposed to answer:

  1. A specific reaction. Export the days around it — the day itself, plus enough days on either side that a reader can see what came before and what happened after. You're not diagnosing anything; you're providing the surrounding context so your pediatrician can.
  2. A general check-in. The period since the last appointment is usually the natural window.
  3. A handover to another caregiver. Recent entries only. They need to know what's been recorded lately, not the full archive.

If you're unsure what window is relevant, export a wider range and say so in a sentence at the top. It's easier for a clinician to skim past extra days than to ask you to go home and look something up again.

What belongs in the file

An export is useful when it answers what, when, and what you observed without editorialising. In practice that means each entry should carry:

What doesn't belong: your theories. If you've written "I think this is the thing causing it" in your notes, that's fine for you, but a clinician reads notes differently when they've already been filtered through a conclusion. Give them the raw record. Let them do the connecting.

Make the file findable later

You will export more than once, and the second export looks exactly like the first in a Files app. Name it like you'll need to find it in a year:

feeding-diary-2025-03-01-to-2025-03-28.pdf

Date ranges in the filename, lowercase, hyphens instead of spaces. If you're handing it to a practice, adding the child's first name helps them file it. Then save a copy somewhere outside your phone — email it to yourself, drop it in whatever cloud folder you already use. The export is a snapshot; the app is the living record, but the snapshot is what someone else saw on that date, and that's worth keeping.

Where exports quietly break

A few things to check before you send:

Pudding keeps the diary on the phone — free, offline, no account — and exporting is the deliberate moment where part of that record leaves the device. Doing it on purpose, with a chosen date range and a sensible filename, is most of the work.

One last thing: a PDF is evidence of what you recorded, not an answer. What it means is a conversation to have with your pediatrician, with the file open in front of both of you.

Pudding is a feeding diary, not medical advice. Make decisions about introducing foods and allergens together with your pediatrician.