Share food photos: what to post and where

Why most food photos get scrolled past

Almost every food photo that fails does so for one of three reasons: it was shot under a ceiling light, it shows a finished plate with nothing happening in it, or it is a picture of a meal rather than a picture of a dish. None of those are camera problems, which is why buying a better camera almost never fixes them.

Overhead kitchen light lands on top of food and flattens it. Every texture you cared about, the crust, the crumb, the gloss on a sauce, is defined by shadow, and a light directly above kills the shadows that would have shown it. Move the plate to a window and shoot with the light coming from behind or beside it and the same dish photographs like a different dish. That single change does more than any edit, and it is covered properly in the food photography guide.

The second failure is stillness. A perfectly composed finished plate is a full stop; there is nothing for a viewer to do with it. Photographs with an action in them, a pour, a pull, a cut, a hand reaching in, steam still rising, hold attention because they imply a next moment. You do not need to fake this. Shoot while you are cooking rather than after you have tidied up.

The third is framing the meal instead of the dish. A whole table shot from standing height, three plates, two glasses, a phone, a corner of the hob, has no subject. Pick one thing, get close enough that it fills the frame, and let the rest be context at the edges.

What is worth posting, and what is not

The useful test is whether somebody could want the thing in the picture. A slightly ugly photograph of an extraordinary bowl of noodles will outperform a beautiful photograph of a mediocre sandwich, every time, on a network where the audience came to look at food.

Things that reliably work: a dish with an obvious technique in it, food in the middle of being made, something regional that most people have not cooked, a repair, the loaf that finally rose after four that did not, and honest domestic cooking that does not pretend to be a restaurant. Things that reliably do not: a plate of something everybody has eaten a thousand times shot from standing height, a photo whose only content is the caption, and anything you did not make or eat, which is the fastest way to lose the trust of a food audience.

The caption is half the post

On Foodies a recipe is a post with a caption. There are no ingredient fields and no numbered step boxes, which means the caption is doing all the work, and a good one has a shape:

Name the dish in the first line. Not "so this happened", the actual name, because the first line is what appears before the fold and it is what somebody searching later will match against.
Say the one thing that matters. Every dish has a hinge: the pasta water, the resting time, the fact that the onions want forty minutes and not ten. Give away the hinge. Withholding it is the behaviour of a content farm.
Give quantities loosely if you give them at all. "Roughly two to one, flour to water" is more useful and more honest than an invented gram figure you did not weigh.
Admit the failure. "The base caught slightly" buys more credibility than any amount of polish, and it is the single most reliable way to start a real comment thread.

Length is not the point; specificity is. Two sharp sentences about why the sear worked beat four paragraphs of atmosphere.

When to post, and how often

Post when you cooked. Hoarding photographs and releasing them on a schedule produces a feed of food you no longer remember making, and captions get vaguer the further they are from the pan. If you batch, batch the shooting rather than the memory: write the caption the same day, even if you post it on Thursday.

Frequency matters less than consistency. Two posts a week for a year builds something; nine in a fortnight and then two months of silence does not, because people follow a rhythm as much as a person. Pick a rate you can hold in a bad week, the guide for food creators goes into cadence in detail.

Likes are applause. Saves are intent.

A like takes half a second and means someone approved. A save means someone intends to make the thing. If you only look at one number, look at saves: it is the closest available proxy for whether your food is actually useful to anybody, and it tends to disagree with likes in informative ways. Dishes that photograph beautifully collect likes. Dishes that solve a problem, the thing to do with half a cabbage, the traybake that survives a Tuesday, collect saves.

Collections: the underused half of the app

Saving is only useful if you can find it again, which is what collections are for. A collection is a named, ordered list you make yourself, and the naming is the entire trick. "Recipes" is a graveyard. "Twenty minutes, nothing in the fridge", "bread I have not managed yet", "for the in-laws" are all retrievable in six months because they describe an occasion rather than a category.

Collections keep the dish and the cook together, so when you open one you get back not just the photograph but the person who made it and whatever they wrote about it. That is the part a screenshot in your camera roll can never give you.

How posting works in Foodies

Pick a photo or a short video, write the caption, post. There is no wizard, no required fields and no multi-step form, because a form is how a dish stops getting posted at all. A post can be a photo or a video; video autoplays muted in the feed and stops the moment you scroll past, which is why the first frame matters more than the first second, the food video guide covers that.

Once it is up, people can like it, comment, save it into their own collections and send it to somebody in a direct message, and anything sent that way is end-to-end encrypted.

Location, and what is public

A post can carry an approximate coordinate, which is what puts it into other people's Nearby feed. Approximate is meant literally: coordinates are snapped to a grid of roughly a kilometre before anything is stored, so a post can say "somewhere in this part of the city" and cannot say "this address". If you decline the location permission, everything else works exactly as before and your posts simply do not appear in Nearby.

Posts, profiles, comments and collections you mark public are public. Direct messages are not, and the server cannot read them. There is no advertising SDK and no analytics broker in the app, so nothing about what you cook is sold or shared onward.

Foodies is free on the App Store

A social network for food and nothing else: photo and video posts, a feed you can steer, live cook-alongs with real-time chat, saves into collections you name yourself, and end-to-end encrypted messages. No ads in the feed. iPhone and iPad, iOS 17 or later, in 34 languages.

Download on the App Store Read the cooking guides first

No restaurant listings, reviews or ratings, Foodies is about what people cook.

Frequently asked questions

What is the best app to share food photos?

It depends on whether you want an archive or an audience. A camera roll or a notes app stores pictures; a food-only social network puts them in front of people who opened an app specifically to look at cooking. Foodies is built for the second case: post a photo or short video, write the method into the caption, and it reaches the people who follow you and, if you allow an approximate location, people near you. It is free on iPhone and iPad.

Is Foodies like Instagram for food?

It is comparable in shape and different in scope. Both are picture-first with follows, likes and comments. The difference is that every post on Foodies is food, so a dish is ranked against other dishes rather than against news and everything else, and the app adds things a general network has no reason to build: saves into named collections, a Food DNA taste summary on profiles, live cook-alongs and end-to-end encrypted messages. There are also no ads in the feed.

What should I write in a food photo caption?

Name the dish in the first line, then give away the one thing that actually makes it work: the resting time, the pasta water, the fact that the onions need forty minutes. Loose quantities are fine and more honest than invented precise ones. Mentioning what went wrong tends to start better conversations than a polished caption does.

How often should I post food photos?

Pick a rate you can hold in a bad week and keep it. Two posts a week sustained for a year builds an audience; a burst of nine posts followed by two months of silence does not, because people follow a rhythm as much as a person. Post close to when you cooked, while you still remember the detail worth writing down.

Why do saves matter more than likes?

A like means someone approved for half a second. A save means someone intends to cook the thing, which is a much stronger signal about whether your food is useful. Saves and likes often disagree: photogenic dishes collect likes, while dishes that solve a real problem collect saves.

Does sharing a food photo reveal where I live?

No. Location on a post is optional, and when it is on, coordinates are snapped to a grid of roughly one kilometre before being stored, so a post can indicate a part of a city but not an address. Declining the location permission leaves every other part of the app working normally; the post simply does not appear in the Nearby feed.

More: the food social network · the foodie community · live cooking streams · food video · cooking guides · about Foodies

How to share food photos people stop for.