Point the phone at the plate. That is all.
- One photo. No scale, no barcode, no food list.
- It asks one question when the photo cannot tell.
- Calories and protein, before you pick up your fork.
One photo. Sometimes one question. That is all you do.
After the photo, the app does the rest.
Take the photo
Snapkin names what is on the plate. It works out portion sizes from the plate and the knife and fork next to it. It also counts the cooking fat and sauce most trackers miss.
Pan-fried, or baked? ±90 kcal
Answer a question, maybe
Sometimes one detail would change the number. Then it asks you. It also tells you how much the answer matters. Tap an answer, or tap "I do not know". You get an estimate either way.
Look at the protein
The calories and macros are added to your day. You see them next to your own targets. Nothing to confirm, nothing to save. Next meal, same photo.
Every question is one tap, and every tap is optional.
Spaghetti and meatballs, and the three questions Snapkin had about it. Tap any answer and watch the estimate change. "I do not know" is always a choice. Then the numbers stay as they are.
Leave it alone and it plays through on its own. It is more fun to tap the answers yourself.
Beef meatballs, or pork? ±45 kcal
Any parmesan on top? ±70 kcal
Did you finish the plate? ±160 kcal
What it reads from a photo
A calorie estimate from a photo means working out three separate things.
- 1. What is on the plate. Not "a plate of food" but each part: the fillet, the rice, the sauce underneath. Each one is a line you can read and correct.
- 2. How much of it there is. The plate or a fork in the photo shows how big things are. So a chicken breast is not a guess between 100 g and 400 g.
- 3. What went in that you cannot see. The oil the pork was fried in. This is where a hand-logged meal is usually off by around two hundred calories. Fried food looks fried.
Restaurant plates, home cooking, a label, half a leftover pizza
Most meals have no barcode. Those are the meals this was built for.
A restaurant plate
Nothing to scan, nothing in any database, and the one meal of the week you most want a number for.
Something you cooked
Photograph the ingredients before they go in the pan. Then photograph the plate afterwards. The estimate gets more precise. Raw rice is easier to judge than a cooked pile of it.
A packet or a nutrition label
Photograph the label. It reads the nutrition table and remembers the brand. The next serving from the same jar takes no effort to log.
Half of something
Ate only part of it? Say so in the note, like "half a portion". Or tell it afterwards: "I left half". The numbers go down.
Several photos of one meal
Attach up to six. They are read together, as one meal, not as six. The plate from above and the label on the sauce jar are two views of the same dinner.
A meal with no photo at all
Describe it in a sentence instead. Less accurate than a photo, but much better than logging nothing.
Try the whole app free for 3 days. Not for you? Cancel, and you pay nothing. €9.99 a month or €99.99 €49.99 a year, via the app.launch price, for a limited time
Point the camera at a menu, not just a plate.
Photographing food is how a meal gets logged. Photographing a fridge or a menu is how you decide what the meal is going to be. Same camera, one screen, three tabs.
Ask for an idea
Say you have 600 calories and 40 grams of protein left, and no idea what to eat. Snapkin names ordinary meals that fit, and shows the calories and protein beside each one.
Photograph your fridge
Take up to three photos: the fridge, the freezer, a cupboard. Snapkin only suggests food it can see in the photos. It also tells you what it could not read.
Photograph the restaurant menu
Snapkin works out the calories for every dish on the menu. It keeps the menu's own courses. It puts the lightest dishes first. It ticks the ones that still fit your day.
A shelf or a menu is further from the camera than a plate. So those numbers are rougher. Snapkin says so on screen, every time.
Oops, I forgot to take a photo of my meal ...
Nothing to worry about. There are still other ways to get your meals into Snapkin.
- 1. Describe it in a sentence. "Two slices of bread with ham, and a coffee with a splash of milk." Say what you know. Whatever you leave out gets estimated.
- 2. "Same as yesterday's breakfast." Written like that, it copies that meal from your history, with the same numbers. This works for meals from the last two days.
- 3. "Roughly 400 kcal, I don't know what was in it." A number on its own is taken as it is. It is marked as a rough guess, and it asks you nothing.
- 4. Had it before? Log it again. Tap plus, then Usual meal. The meals you are most likely to eat are waiting, with their photos. Tap one, check the portion, and it is logged with your usual numbers for it.
A described meal is a rougher estimate, and it says so.
It usually gets a lower rating, like "Rough guess". You can still see each item and undo it. No meal counts for less.
Take the photo at the table. Log it from the couch.
The photo takes two seconds. Nobody at the table notices. Later, on the couch, you go through the day in one go. Answer its questions. Fix a portion it got too big. Done.
No signal, or the app closes? Your meal is safe
Snapkin saves the photo on your phone first. Then it sends it. No signal? On a plane? The app closed halfway? The photo waits on your phone. It uploads the next time you open the app. It lands on the day and time you took the photo. You are back on your day straight away. The numbers arrive while you eat.
Photograph one meal and see
It's that simple. It keeps working through restaurants, holidays and busy weeks. There is nothing else to keep up with.
Try the whole app free for 3 days. Not for you? Cancel, and you pay nothing. €9.99 a month or €99.99 €49.99 a year, via the app.launch price, for a limited time