Chapter 25: Mobile Editing: Processing and Publishing from Your Phone

"The negative is the equivalent of the composer's score, and the print the performance." — attributed to Ansel Adams

Overview

You made the photograph. Maybe it was the long exposure from the last chapter, the blue-hour cityscape, the portrait by the kitchen window. You have the file. And then — for an enormous number of people — the file sits there, untouched, straight out of the camera, which is a little like a musician handing you the sheet music and calling it a concert. The capture is the score. The edit is the performance. This chapter is about giving the performance, and giving it on the only instrument that is always in your pocket.

Here is the claim that organizes everything ahead: a phone is a darkroom. Not a toy version of one, not a stepping stone to the "real" software on a desktop — a genuine, complete darkroom that fits in your hand, runs on a battery, and can take a flat RAW file to a finished, printable, shareable image without you ever sitting at a computer. The screen is small and a touchscreen is a blunt instrument compared to a mouse, and we will be honest about both of those limits all chapter. But the operations are the same operations. The decisions are the same decisions. A photographer who can develop an image well on a phone can develop it well anywhere, because the hard part was never the software — it was knowing what the picture needed.

That knowing is what we build here. We will not memorize the menus of any one app, because apps change their menus every year and we are writing principles that outlast them. Instead you will learn the order in which a photograph gets developed, the difference between a global change and a local one, how to capture a look so you can repeat it, and how to hand the finished file to a print lab, a website, and a social feed — three destinations that each want something different and will quietly ruin your image if you give them the wrong thing. By the end you will run the whole pipeline, start to finish, on the device you already own.

In this chapter, you will learn to:

• Assemble a small, deliberate mobile editing toolkit and understand what each kind of app is for.
• Develop a phone RAW file in a repeatable order — the same global develop pass a desktop uses, done by touch.
• Make local adjustments: paint, mask, and select parts of the frame so your edit guides the eye instead of flattening the whole picture equally.
• Build and apply a preset so a set of images shares one look — and know when a preset helps and when it lies.
• Export correctly for each platform: choose the aspect ratio, the resolution, and the output sharpening that the destination actually wants.
• Run a complete mobile edit end to end, and recognize the specific ways a phone screen will fool you.

Learning Paths

📱 Mobile-only: This is your chapter — arguably the chapter the whole book has been pointing you toward. Everything here is your primary workflow, not a compromise. Read all six sections; §25.2 (the RAW workflow) and §25.6 (the complete edit) are where you turn the phone into a finishing tool that rivals a desktop. 🎨 Hobbyist: Even if you edit mainly on a computer, mobile editing is how you finish the photo you took an hour ago on the trail and want to share tonight. Focus on §25.2–§25.3 and the export rules in §25.5 so your shared images stop looking soft and over-compressed. 💼 Pro-track: Clients increasingly want a same-day "selects" gallery from the field. Master §25.4 (presets for consistency across a take) and §25.5 (platform-correct export and sharpening) — turning around a coherent, properly-sized set from a phone on location is a real, billable skill. 🎓 Student: The Portfolio Checkpoint asks for a finished mobile edit you will later compare to a desktop edit, so work §25.2 and §25.6 carefully and keep notes on every slider you moved. The Summary and key-takeaways card are your revision anchors.

25.1 The mobile editing toolkit: what the apps actually do

Before you move a single slider, you need to know what is on the workbench. Walk into any app store and search "photo editor" and you will drown — thousands of apps, most of them filters-with-a-logo, a few of them serious darkrooms. The confusion is not a software problem; it is a categories problem. There are only four kinds of mobile photo app, and once you can sort any app into the right bucket, the whole landscape becomes legible. You do not need many apps. Most working mobile photographers do everything in one, maybe two.

The four categories.

FIGURE 25.1 — The four kinds of mobile photo app

  ┌─────────────────────────┐      ┌─────────────────────────┐
  │  1. THE CAMERA APP       │      │  2. THE DEVELOPER        │
  │  (capture)               │ ───► │  (the darkroom)          │
  │  • shoots RAW / ProRAW   │      │  • global tone & color   │
  │  • manual control        │      │  • local adjustments     │
  │  • the native camera or  │      │  • presets, export       │
  │    a "pro camera" app    │      │  • THIS is where you live │
  └─────────────────────────┘      └─────────────────────────┘
                                              │
                 ┌────────────────────────────┼───────────────┐
                 ▼                                             ▼
  ┌─────────────────────────┐      ┌─────────────────────────┐
  │  3. THE SPECIALIST       │      │  4. THE PUBLISHER        │
  │  • one job, done well    │      │  • the social app itself │
  │  • B&W, double-exposure, │      │  • re-compresses & resizes│
  │    sky replacement,      │      │  • applies ITS own crop  │
  │    healing, panorama     │      │  • where export goes     │
  └─────────────────────────┘      └─────────────────────────┘

  You can run the entire book's mobile workflow inside #2 alone.
  #1 you may already own (native camera). #3 and #4 are situational.

A camera app captures — it is where you set exposure, lock focus, and choose to shoot RAW, all of which you learned to drive in Chapter 22. A developer is the darkroom: it takes the captured file and lets you adjust tone, color, and sharpness globally and locally, save looks, and export. This is the app you will spend ninety percent of your editing life inside, and choosing one good one matters more than owning ten mediocre ones. A specialist does a single thing exceptionally — a dedicated black-and-white converter, a healing/object-removal tool, a panorama stitcher — and you reach for it only when the developer can't do that one job well enough. The publisher is the social platform itself, and here is the part most people miss: the publisher is also an editor, whether you want it to be or not. It will re-compress your file, often resize it, and impose its own crop. Half of "why does my photo look worse after I post it" is the publisher silently re-editing what you uploaded. We tame that in §25.5.

🎒 Gear Note: You do not need to buy your way into mobile editing, and you should resist the instinct to. A serious, full-featured mobile developer is available free or nearly so; the paid tiers mostly add cloud sync and a few advanced masks, not better fundamentals. The single most consequential choice is picking one developer that (a) accepts RAW files, (b) offers true local adjustments (masks/brushes), and (c) lets you save and reapply your own presets. Those three capabilities define a real darkroom. Anything calling itself a "filter app" that lacks them is a category-3 specialist at best — fine for fun, wrong as your main workbench. Learn one good developer deeply rather than collecting twenty you use shallowly; the skill transfers, the specific app does not.

What "non-destructive" means on a phone — and why it's the feature that matters most. Every serious mobile developer edits non-destructively, the same principle the digital darkroom runs on (we go deep on it in Chapter 26). It means your edits are stored as a list of instructions applied on top of the original file, never baked into the pixels until you export. The original is always there underneath, pristine. You can dial exposure to +1.5 today, decide tomorrow it was too much, and slide it back to +0.8 with zero loss — because you never actually changed the photo, only the recipe sitting on top of it. This is why you should be deeply suspicious of any "editor" that opens your photo, lets you slap a filter on, and saves over it: that is destructive, irreversible, and amateur. The darkroom keeps the negative. So does your phone, if you let it.

🔄 Check Your Eye: 1. You download an app that lets you apply a filter and immediately saves the result over your original photo, with no way to dial the filter back later. Which of the four categories is it, and why is it the wrong choice for your main workbench? 2. Name the three capabilities that distinguish a real "developer" from a mere filter app.

Answers

1. It behaves like a category-3 specialist (or worse, a novelty filter) and is editing destructively — baking the change into the pixels with no non-destructive history. Your main developer must keep the original untouched so every edit is reversible. 2. It must (a) accept RAW files, (b) offer true local adjustments (masks/brushes/selections), and (c) let you save and reapply your own presets.

25.2 The mobile RAW workflow: developing flat data in a repeatable order

Open a RAW file you shot on your phone and your first reaction may be disappointment: it looks flat, grey, lifeless — worse, somehow, than the cheerful JPEG the phone showed you in the camera app. Do not panic. That flatness is the whole point, and learning to love it is the gateway to real editing.

What mobile RAW is. A mobile RAW file (Apple markets its version as ProRAW; Android phones expose RAW as DNG) is the relatively unprocessed data straight off the phone's sensor, saved before the phone applies its usual punchy contrast, saturation, and sharpening. Where a JPEG is a finished interpretation the phone made for you — baked, committed, hard to undo — a RAW is the raw ingredients with the cooking left up to you. You met this idea for the camera back in Chapter 2 and chose to shoot it on the phone in Chapter 22; now you find out why you bothered. The flat RAW holds far more recoverable information in its brightest highlights and darkest shadows than the JPEG does. That blown-out sky the JPEG threw away? The RAW probably still has the clouds. That black shadow under the bridge? The RAW can lift it and find detail. The flatness is not a defect. It is latitude — room to make decisions — and the JPEG spent that latitude for you before you got a vote.

🔬 The Physics: (Optional — skip without penalty.) Why does a RAW hold more than a JPEG? Two reasons, both about how many distinct brightness levels survive. First, bit depth: a standard JPEG records 8 bits per color channel — 256 levels per channel — while a phone RAW typically captures 10 to 14 bits, meaning 1,024 to 16,384 levels. More levels means smoother gradients and far more room to push tones around before the image breaks into banding. Second, the JPEG is the output of the phone's tone-mapping and compression — highlights already rolled off, shadows already crushed, and lossy compression having discarded fine differences your eye "probably won't miss." The RAW skips all of that. The cost is file size (a RAW is many times larger) and that the file requires developing — it is exposed film, not a print. We unpack bit depth and the histogram further in Chapter 26's Physics box.

The order of operations is the whole skill. Beginners edit by wandering — nudge saturation, then exposure, then a random filter, then back to saturation because the filter changed it, chasing their own tail. Professionals develop in a fixed order, because each step changes what the next step should be, and doing them out of order means redoing them. Here is the repeatable global-develop order, the same sequence a desktop uses (Chapter 26 formalizes it), executed by touch on a phone:

FIGURE 25.2 — The mobile RAW develop order (top to bottom; do it in this sequence)

  STEP                  THE TOUCH CONTROL              THE DECISION YOU'RE MAKING
  ─────────────────────────────────────────────────────────────────────────────
  1. White balance      Temp + Tint sliders            "Is the light's color honest /
                        (or tap a neutral grey)         the mood I want?"
  2. Overall exposure   Exposure / Brightness          "Is the whole image too dark or
                                                         too bright?"  ── watch histogram
  3. Recover the ends   Highlights ↓ , Shadows ↑       "Pull back the blown sky; open the
                        (then Whites / Blacks)          crushed shadows — find the detail"
  4. Contrast & curve   Contrast slider / Tone Curve   "Set the punch — the spread from
                                                         darkest to lightest"
  5. Presence           Texture, Clarity, Dehaze       "Local contrast — crispness and
                                                         'bite' without over-sharpening"
  6. Color              Saturation / Vibrance, then     "Make color accurate, then
                        per-color HSL                    expressive; tame the loud ones"
  7. THEN local + crop  (next section) + straighten     "Now guide the eye to specific
                                                         areas; fix the frame"

  Rule of thumb: GLOBAL before LOCAL, and TONE before COLOR.
  You can revisit any step — it's non-destructive — but START in this order.

Walk down it once and the logic is obvious. White balance first, because the color temperature of the light (Chapter 5) tints everything; set it wrong and every color decision after it is built on a lie. Then overall exposure, watching the histogram you learned to read in Chapter 3 — is the whole image too dark, too bright? Get the bulk of the tones sitting where you want before you fuss with the extremes. Then recover the ends: pull Highlights down to rescue a bright sky, push Shadows up to open dark corners — this is where the RAW's latitude pays you back, and it is the single biggest reason to have shot RAW at all. Then contrast, the spread from black to white, set globally with a slider or precisely with a tone curve. Then presence — Texture, Clarity, Dehaze, the local-contrast controls that add crispness and bite. Then color, accurate first (correct any cast) and expressive second (vibrance to lift the muted tones, then per-color HSL to tame the one screaming hue). Only after all of that do you crop and go local.

The two rules that keep you out of trouble: global before local, and tone before color. Fix the whole image's brightness and contrast before you start painting on individual areas, and settle the brightness/contrast before you push saturation — because contrast changes apparent saturation, so doing color first means doing it twice.

⚠️ Common Mistake: Slamming the saturation slider first (and to +60). It is the most tempting control and the most destructive habit. Saturation cranked early makes a flat RAW instantly "pop," so beginners reach for it before fixing exposure or white balance — and then everything downstream fights it. Worse, global saturation pushes every color equally, so skies go radioactive and skin goes orange together. The fix is discipline of order (color comes near the end, step 6) and discipline of tool: reach for Vibrance before Saturation. Vibrance is a smarter, protective version — it lifts the muted colors more and the already-saturated ones less, and most implementations specifically protect skin tones from going orange. If your edits look garish, you almost certainly did color too early and too globally.

Let us make a develop pass concrete with a frame from a location you know — the city block at night from Chapter 21.

🖼️ Read This Frame:

text FIGURE 25.3 — "Blue-hour street, before and after the develop pass" [constructed teaching example] THE FRAME A wet city street recedes from the bottom edge to a cluster of neon signs three blocks back; parked cars line the right, a lit shop window glows on the left. Shot vertical on a phone, handheld, just after sunset. THE LIGHT Mixed and tricky: warm orange sodium streetlights, cool blue dusk sky, a green-tinged fluorescent shop interior, magenta-pink neon. No single white point — the classic mixed-lighting problem (Chapter 15). THE MOMENT Blue hour, the ten-minute window where the sky still holds deep blue and the artificial lights have come on — the city at its most balanced. THE BEFORE The RAW opens flat and muddy: the sky is a washed grey-blue, the neon is dull, the wet pavement reads as a dark featureless smear, and an overall sickly green cast (from the phone's confused auto white balance) sits over everything. THE DEVELOP (1) White balance: cooled slightly and pulled the Tint off green toward magenta — the sky snaps to true deep blue. (2) Exposure: down a touch; the phone over-brightened the dusk. (3) Highlights down to stop the neon and shop window from blowing out; Shadows up to find the texture of the wet bricks. (4) Contrast up modestly. (5) Texture up to bring out the reflections on the wet street; Dehaze a hair to cut the dusk murk. (6) Vibrance up to make the neon sing; then HSL — pulled the green of the fluorescent down so the shop stops fighting the scene. THE EFFECT The eye now travels the wet street's reflections straight back to the glowing neon cluster, the deep blue sky frames the warm lights, and the whole frame reads as the city you actually stood in — which the flat RAW never did, and the punchy JPEG would have faked in the wrong direction (green cast baked in, highlights gone). THE LESSON The develop pass does not "fix" the photo — it *reveals* the photograph that was latent in the RAW data. The flat file was not worse than the JPEG; it was the negative, waiting for the print. Order of operations turned a muddy smear into the scene you saw.

📸 In the Field: Shoot one scene with real tonal range — a window-lit interior looking out to a bright outside, a tree against a bright sky, anything with both deep shadow and bright highlight — and shoot it twice on your phone: once as a normal JPEG, once as RAW. Then develop only the RAW, walking the seven-step order in Figure 25.2, and specifically try to recover detail in the brightest and darkest parts. Lay the two finished images side by side. The JPEG can't be pushed nearly as far before the sky goes white and the shadows go to mud; the RAW holds detail you can pull back. Keep both, labeled, as your personal proof of why RAW is worth the storage. Shoot 1 scene, develop 1 RAW, and write one sentence on the biggest difference you found.

25.3 Local adjustments on a touchscreen: editing the eye's path with your finger

Everything in §25.2 was global — every slider changed the entire frame at once. But great editing is rarely uniform. A landscape often wants the sky one stop darker and the foreground one stop brighter. A portrait wants the eyes brightened and a distracting bright patch in the corner toned down. The face of a subject wants warmth; the background can stay cool. The tool for all of this is the local adjustment: a change applied to a selected part of the frame rather than the whole image. If global edits set the stage, local edits are where you direct the actors.

Why local editing is the secret of professional-looking images. Think back to the very first chapter: the eye goes to what is brightest and sharpest. Local adjustments are how you control exactly that. You can brighten the subject and darken everything else, and the viewer's eye snaps to the subject without ever knowing why. You can add a touch of clarity to the one face that matters and leave the crowd soft. The photograph stops being evenly lit information and starts being guided — which is the entire difference between a snapshot and a directed image. Local editing is composition continued by other means, after the shutter.

The four ways to select an area by touch. Every mobile developer gives you some combination of these. The names vary; the logic does not.

FIGURE 25.4 — The four local-selection tools (and what each is for)

  TOOL              HOW IT SELECTS                  BEST FOR
  ──────────────────────────────────────────────────────────────────────
  ◯ Radial /        An oval you place and size;     A single subject, a face,
    Elliptical      effect inside (or outside) it    a glow around a light source
  ───────────────────────────────────────────────────────────────────────
  ▭ Linear /        A graduated band; effect fades   Skies, horizons, anything
    Graduated       across it from full to none      that changes top-to-bottom
  ───────────────────────────────────────────────────────────────────────
  ✎ Brush           You paint the selection with     Irregular shapes — a person,
                    your fingertip                   a building edge, exact areas
  ───────────────────────────────────────────────────────────────────────
  ⚙ Auto / AI       The app detects "sky," "subject, Fast, scene-aware masks;
    mask            "background," "skin" for you     verify the edges before trusting

A radial mask is an oval you drop over a subject — brighten inside it to spotlight a face, or invert it to darken everything outside a vignette that pulls the eye inward. A linear (graduated) mask is a band whose effect fades smoothly from full strength to nothing across it — the digital version of the graduated neutral-density filter from the landscape chapter (Chapter 16), perfect for pulling a bright sky down a stop while leaving the land untouched. A brush lets you paint the selection freehand with your fingertip, which is the only way to follow an irregular edge like a person's outline or a roofline. And increasingly, auto/AI masks detect "the sky," "the subject," "the background," or "skin" and build the selection for you in one tap — astonishingly useful, and worth verifying, because the machine sometimes grabs a sliver of the wrong thing along a tricky edge (we look hard at where these selections fail in Chapter 23).

The touchscreen technique that separates clean local edits from sloppy ones. A finger is fat and a phone screen is small, so two habits make all the difference. First, pinch to zoom in before you brush — get right up to the edge you are painting so you can be precise, then zoom back out to judge the whole effect. Second, feather your masks. Feathering softens the boundary of a selection so the adjustment fades in instead of stopping at a hard, obvious line. An unfeathered local edit announces itself — a visible halo around a brightened subject, a hard seam where the darkened sky meets the trees. A feathered one is invisible; the viewer feels the guidance without seeing the technique. The goal of local editing is that no one can tell you did it.

💡 Why It Works: A darkened edge and a brightened center is not a trick — it is how the eye is built. Human vision is drawn to local contrast and to brightness; a subject that is even slightly brighter than its surroundings reads as "important" before the conscious mind has decided anything. This is the same mechanism behind a spotlight on a stage, the vignette in a Renaissance painting, and the rim of light a studio photographer puts behind a subject (Chapter 12). When you brighten the subject and gently darken the rest with a local adjustment, you are not faking attention — you are arranging the photograph so attention falls where you decided it should. That is the post-capture half of the compositional control you learned in Part II.

♿ Accessibility & Inclusion: Local editing of people demands the same care as photographing them. When you brighten or warm a face, do it consistently and respectfully across skin tones — be especially wary of "auto skin smoothing" and "face brightening" features, many of which were tuned on a narrow range of skin tones and will lighten or distort deeper complexions in ways their owners did not consent to and do not want. Edit toward the person as they actually are, not toward a default the software prefers. And when you publish (the next chapter on your toolkit, and Chapter 34), write a real image description / alt text for the finished frame — naming the subject, the light, and the action — so blind and low-vision viewers reach the same photograph everyone else does. Describing your own local edits in words ("the eyes lifted half a stop, the busy background pulled down") is also the fastest way to learn to see whether they worked.

🔄 Check Your Eye: 1. You want to pull a too-bright sky down by a stop while leaving the landscape below it untouched. Which of the four selection tools is the natural fit, and what is the digital "filter" it imitates from the landscape chapter? 2. What does feathering a mask do, and why does an unfeathered local edit look amateurish?

Answers

1. A linear/graduated mask — its effect fades smoothly across the band, so you can darken the sky and let the adjustment fall to zero at the horizon. It imitates the graduated neutral-density (graduated ND) filter from Chapter 16. 2. Feathering softens the selection's boundary so the adjustment fades in gradually rather than stopping at a hard line; without it you get a visible halo or seam where the edited area meets the unedited area, which announces the manipulation and reads as sloppy. The aim is an invisible edit.

25.4 Presets, looks, and consistency: editing a body of work, not one frame

You have now developed one image, by hand, slider by slider. Imagine doing that from scratch for forty photographs from one shoot, trying to make them feel like they belong together. You would drift — image three would end up warmer than image thirty, the contrast would wander — and the set would look like forty separate edits, because it would be. The tool that solves this is the preset.

What a preset is. A preset is a saved bundle of edit settings — your whole develop recipe — that you can apply to another image in one tap. You develop one photo until you love it, save those settings as a preset ("Blue Hour Street," "Warm Portrait," "Punchy Landscape"), and then apply that same starting point to every other image from the shoot. In one move, all of them get the same white-balance shift, the same tone curve, the same color treatment. It is the difference between hand-mixing paint for every wall of a house and mixing one bucket and using it throughout.

But a preset is the beginning of an edit, not the end of one, and confusing those two is the central mistake.

⚠️ Common Mistake: Treating a preset as a one-tap finish. A preset is a starting point applied to many images — it cannot know that photo #1 was shot in shade and photo #2 in sun, that one is two stops brighter than the next. The right workflow is: apply the preset to give the whole set a shared look, then go through and adjust the exposure of each image individually so they match in brightness. The preset handles the style (color, contrast, mood); you still handle the exposure per frame, because exposure varies shot to shot and style shouldn't. People who skip the per-image exposure tweak end up with a "set" where the look is consistent but the brightness lurches around — which somehow looks worse than no preset at all, because the consistency of the color makes the inconsistency of the exposure glaring. Preset for the look; hand-finish the exposure.

Where presets come from, and the honest truth about the ones you buy. You can build your own (the best way — your presets encode your taste and grow with you), use the ones built into your developer, or buy "preset packs" sold by photographers and influencers. The packs are not a scam exactly, but understand what you are buying: a set of slider positions tuned for the seller's photos, shot in their light, often of their kind of subject. Dropped onto your differently-lit images they rarely look like the marketing examples, because the marketing examples were also hand-finished after the preset. A purchased preset is at most a tasteful starting point you must then adapt — never a shortcut to someone else's results. The far more valuable habit is building your own as you go: every time you finish an edit you genuinely love, save it as a preset, and over a year you accumulate a personal palette of looks that are yours. This is, quietly, one of the first concrete steps toward the personal style we chase in Chapter 39.

Consistency without sameness. The goal of a preset is a coherent body of work, not forty identical images. A good preset gives a set a recognizable family resemblance — a consistent color signature, a consistent contrast — the way a film stock used to give every frame on the roll a shared character. It should not flatten every image into the same thing; a portrait and a landscape from the same shoot can share your color signature while still being a portrait and a landscape. Consistency is a through-line, not a uniform. When you sequence a portfolio later (Chapter 34) or build a long-term project (Chapter 38), this shared signature is part of what makes a collection read as one voice instead of a pile of unrelated pictures.

🔗 Connection: The "build your own preset" habit connects directly to two later chapters. In Chapter 27 you'll learn color grading — the deliberate shaping of color for mood — which is exactly the kind of decision a preset captures and repeats. And in Chapter 39, "Finding Your Voice," a consistent editing signature across your work is named as one of the things that make a body of work recognizably yours. A preset is how you make a hard-won look repeatable; consistency of look is part of how style becomes visible.

🔄 Check Your Eye: 1. You apply your "Golden Trail" preset to twelve hike photos and they all share a lovely warm look — but some look too dark and some too bright. What step did the preset not do for you, and what must you do by hand? 2. Why does a preset you bought from a photographer rarely look like the example images on their sales page?

Answers

1. The preset set the style (color, contrast, mood) identically across all twelve, but it could not set the exposure correctly per image, because brightness varied shot to shot. You must go through and adjust each image's exposure individually so they match in brightness. 2. The preset's slider positions were tuned for the seller's photos, light, and subjects; on your differently-lit images they land differently. The sales examples were also hand-finished after the preset, so the preset alone never reproduces them — it's a starting point you adapt, not a finished result.

25.5 Exporting for each platform: handing the file to print, web, and social

Your edit is done. Now you have to get it out of the app and to its destination — and this last step, which beginners treat as an afterthought (just hit "save," right?), is where an enormous amount of good work quietly dies. The reason your beautifully edited photo looks soft, muddy, or weirdly cropped after you post it is almost always an export/resize mistake — a decision you didn't know you were making, made wrongly by default. Three things have to be right, and each destination wants them set differently: the aspect ratio, the resolution, and the output sharpening.

Export/resize — the decision you're actually making. To export/resize is to produce a new file from your non-destructive edit at a chosen size and format, sized and compressed for a specific destination. You are not "saving the photo" — the photo (your edit recipe on the original) stays in the app. You are generating a flattened copy at, say, 2,048 pixels on the long edge, in JPEG, for Instagram. Get the size and format right for where it's going and the image survives the trip; get it wrong and the destination mangles it.

Aspect ratio: shape the frame for where it lives. The aspect ratio (platform) is the shape of the frame — the ratio of width to height — and different destinations display, or forcibly crop to, different shapes. Hand a platform the wrong shape and it will crop your image, choosing what to cut with no regard for your composition. The fix is to crop deliberately in your editor before export, so you control the cut, not the algorithm. The common shapes:

FIGURE 25.5 — Common aspect ratios and where they live

  RATIO     SHAPE              TYPICAL HOME
  ──────────────────────────────────────────────────────────────
  3:2       ┌────────┐         The classic camera frame; most prints
            └────────┘         (4×6 print is 3:2). Native to most cameras.
  ──────────────────────────────────────────────────────────────
  4:5       ┌──────┐           The "portrait" feed post — tallest a social
            │      │           feed usually allows; maximizes screen space.
            └──────┘
  ──────────────────────────────────────────────────────────────
  1:1       ┌─────┐            The square; old-Instagram, many grids,
            │     │            profile thumbnails.
            └─────┘
  ──────────────────────────────────────────────────────────────
  9:16      ┌───┐              Vertical full-screen — stories, reels, the
            │   │              phone held upright, edge to edge.
            │   │
            └───┘
  ──────────────────────────────────────────────────────────────
  16:9      ┌──────────┐       Widescreen — video thumbnails, some web
            └──────────┘       headers, anything cinematic/landscape.

  Crop to the destination's ratio IN YOUR EDITOR, on purpose,
  so the platform never crops it FOR you.

Resolution: big enough to be sharp, small enough to travel. Resolution is how many pixels the exported file contains, and the right number depends entirely on the destination. For social and web, you want the long edge somewhere around 2,000–2,560 pixels: large enough that the image is crisp on a high-resolution phone screen, small enough that the platform doesn't have to aggressively re-compress it. (Counter-intuitively, uploading a gigantic 8,000-pixel file to social media often looks worse than a right-sized one, because the platform re-compresses the giant file harder and cruder than you would.) For a print, the logic flips: you want all the pixels, exported at full resolution, because the print lab needs roughly 240–300 pixels per inch of paper to look sharp — a 12-inch print needs on the order of 3,000 pixels on that edge. The rule: social wants small-enough; print wants everything.

Output sharpening: the last touch, and it's destination-specific. Here is the subtle one. Sharpening for output is a final, small sharpening pass applied on export, tuned to how the image will be viewed — and it is separate from any sharpening you did while developing. The reason it exists: the act of resizing an image down for the web softens it slightly (the resampling blurs fine edges), and printing on paper softens it too (ink spreads into the fibers). A touch of output sharpening counteracts that specific softening. The catch is that screen and paper need different amounts: a screen-bound image needs a modest sharpen for the resize; a print needs a stronger one to fight ink spread, and even more for matte paper than for glossy. Most mobile developers bury this in the export dialog as a "Sharpen for: Screen / Print (Glossy) / Print (Matte)" option — find it, and set it to match the destination. Sharpen for screen and send it to print and it looks soft; sharpen for matte print and post it to social and it looks crunchy and over-edged.

⚙️ Settings Box — Export targets at a glance (starting points to adjust, not laws)

Destination	Aspect ratio	Long edge	Format	Output sharpening
Instagram feed (portrait)	4:5	~2,048 px	JPEG, high quality	Screen (modest)
Instagram square	1:1	~2,048 px	JPEG	Screen
Stories / Reels / TikTok	9:16	~1,920 px wide	JPEG	Screen
Portfolio website	3:2 or as composed	~2,560 px	JPEG, high quality	Screen
Email / messaging	as composed	~1,600 px	JPEG	Screen (light)
Print, small (4×6 / 5×7)	3:2	full resolution	JPEG or TIFF, max	Print (match paper)
Print, large (12×18+)	3:2 or as composed	full resolution	TIFF if offered	Print (Matte/Glossy)
Archive / re-edit later	original	full / original	keep RAW + a max-quality copy	none

When in doubt: smaller and right-sized for screens; everything you have for paper. Always keep the RAW and your non-destructive edit — the exported JPEG is a delivery copy, never your master.

🔗 Connection: The aspect ratios here are the same ones that govern how you sequence and present a body of work in Chapter 34, "Sharing Your Work." Knowing a feed wants 4:5 and a print wants 3:2 isn't just a technical export detail — it shapes how you compose, because a photo destined for a 9:16 story should have been framed with that tall shape in mind. Export is where capture, edit, and audience meet.

🔄 Check Your Eye: 1. You export a finished photo at 8,000 pixels on the long edge and upload it to Instagram; a friend exports the same image at 2,048 pixels. Whose looks sharper in the feed, and why? 2. You're sending an image to a matte-paper print lab. Name the two export settings that differ most from how you'd export the same image for the web.

Answers

1. The friend's 2,048-pixel version usually looks sharper, because the platform re-compresses the giant 8,000-pixel file more aggressively and crudely than a right-sized one — over-large uploads often come out worse. 2. Resolution (full/maximum for print vs. ~2,000 px for web) and output sharpening (a stronger "Print — Matte" sharpen to fight ink spread vs. a modest "Screen" sharpen). Format may also differ (TIFF/max-quality JPEG for print).

25.6 A complete mobile edit, start to finish

Now we put all five sections together and run one image from capture to publish without ever touching a computer. We'll use the recurring kitchen window location and the most ordinary subject imaginable, to prove the point one more time: the photograph is made by decisions, and the phone can execute every one of them, capture through delivery.

The capture (a quick recap of Chapters 5 and 22). You set a coffee cup on the counter beside the kitchen window in the late-afternoon light, turned it until the soft light rakes across it from the side (Chapter 5), tapped to focus on the rim, locked exposure, and shot it as RAW (Chapter 22). You have a flat, latitude-rich file. Now we develop it.

FIGURE 25.6 — The complete mobile edit, as a pipeline

  CAPTURE ──► IMPORT ──► GLOBAL DEVELOP ──► LOCAL ──► CROP ──► PRESET? ──► EXPORT ──► PUBLISH
  (RAW)       (into the   (the 6 steps of    (brush/   (frame   (save the   (per-      (and the
              developer)   Figure 25.2,       mask the  for the  recipe to   platform   platform
                           in order)          subject)  target)  reuse)      target)    re-edits!)

  Capture/import/develop you've met. The new muscle is doing it ALL on the phone,
  in order, and exporting correctly. Below, each phase with the thinking.

Phase 1 — Global develop, in order (§25.2). White balance first: the late-afternoon window light is warm, and you decide to keep a little of that warmth because it's the mood, so you nudge temperature only slightly cooler to correct the worst of the orange, not all of it. Exposure: the RAW came in a hair dark; up a touch, watching the histogram so the highlight on the cup's rim doesn't clip. Recover the ends: highlights down a little to hold detail in that bright rim, shadows up to open the dark side of the cup so it doesn't go to a featureless black. Contrast up modestly for some punch. Texture up a little to bring out the ceramic's surface and the faint steam. Color last: vibrance up gently — the cup is a muted blue and you want it to read, not glow.

Phase 2 — Local adjustments (§25.3). Now the directing. The cup is the subject, so you place a radial mask over it and lift its exposure a third of a stop — just enough that the eye goes there first. You brush a reduction in exposure over the bright, distracting patch of countertop in the lower corner that was pulling the eye away. You zoom in, brush a touch of extra texture onto the rising steam so it catches. Every one of these is invisible if done right — feathered, subtle — and together they turn an evenly-lit record into a directed image.

FIGURE 25.7 — "Kitchen-window cup, finished"      [constructed teaching example]
  THE FRAME    A single muted-blue ceramic cup sits right of center on a wooden counter, a thread of steam
               rising from it, the kitchen falling into soft shadow behind. Shot 4:5 (portrait), close.
  THE LIGHT    Soft late-afternoon window light raking from camera-left; the near side of the cup bright,
               the far side gently shadowed, a small specular highlight on the wet rim. Warm, but corrected
               down to "warm-neutral."
  THE MOMENT   Steam caught mid-rise — the develop pass (texture, local brush) is what made the nearly
               invisible steam read at all.
  THE CHOICES  RAW captured for latitude; developed in order (WB → exposure → recover → contrast → texture →
               color); cup lifted with a radial mask, distracting counter-patch brushed down; cropped 4:5 for
               the feed; exported 2,048 px, screen sharpening.
  THE EFFECT   The eye lands on the bright, slightly-lifted cup and its rim highlight, follows the steam up,
               then settles into the soft shadow behind. An object you'd ignore on the counter becomes a
               quiet, intentional still life — and it never left the kitchen or the phone.
  THE LESSON   The full darkroom fits in your hand. Capture for latitude, develop in order, direct the eye
               locally, export for the destination — the entire pipeline, start to publish, on the device in
               your pocket. The cup is the red door's cousin: an ordinary subject made by decisions, not gear.

Phase 3 — Crop and preset (§25.4). You crop to 4:5 because this one's going to the feed, framing so the cup sits on a power point (Chapter 6) and the steam has room to rise into negative space. You love this warm, soft, slightly-lifted look — so you save the whole recipe as a preset called "Window Still Life," and now the next twenty kitchen shots can start from here.

Phase 4 — Export and publish (§25.5). Export at 4:5, 2,048 pixels long edge, JPEG high quality, screen sharpening — the right copy for a feed. You also export a full-resolution copy with print sharpening, just in case you want a 5×7 print later, and you keep the RAW and the non-destructive edit as your master. Then you publish — and you remember the lesson of §25.1: the platform will re-compress and may re-crop. Because you already cropped to 4:5 and sized to ~2,048 px, you've handed it exactly what it wants, so it has little left to ruin.

🎞️ Behind the Image: (A constructed but representative vignette.) The reason this whole pipeline matters isn't the cup — it's the bus. Picture finishing a shoot on a trail, getting on the bus home, and by the time you reach your stop having developed three RAW files, directed the eye in each with a couple of local brushes, applied a shared preset so they read as a set, exported them correctly for the feed, and posted them — all on the ride, all on the phone, the images finished and shared before you'd have even reached a computer. That is not a worse version of "real" editing. For an enormous amount of working photography now, it is the editing. The darkroom used to be a room you went to. Now it's a thing you carry, and the only thing that's changed is that the performance can happen anywhere the score was written.

🚪 Threshold Concept: The capture is the negative; the edit is the print; and you now own a complete darkroom that runs on a battery. Once you truly believe a phone can take a RAW file to a finished, print-ready, platform-correct image — not as a compromise but as a full workflow — your relationship to "needing a computer to make real photographs" dissolves. The constraint was never the device. It was, as it has been since Chapter 1, whether you know what the picture needs. You do now. The rest is your finger on the glass.

📸 In the Field: Run the whole pipeline once, deliberately, exactly as this section describes. Pick one keeper-worthy RAW you've already shot (or go shoot one at your kitchen window). Develop it in order; make at least two local adjustments that direct the eye; crop it for one specific destination; save your settings as a named preset; export it correctly for that destination; and publish or place it. Keep notes on every step. This single run-through is your Portfolio Checkpoint below — and the foundation of every mobile edit you'll ever do.

Portfolio Checkpoint

Your portfolio now holds keepers shot in many conditions — a golden-hour frame, a portrait, a long exposure, a phone-only image. This chapter doesn't add a new capture; it adds a finished edit, and a benchmark.

Produce a finished mobile edit of one keeper. Take one of your existing portfolio images — ideally one you shot in RAW (the long exposure from Chapter 21 or the phone-only frame from Chapter 22 are perfect candidates) — and develop it to a finished state entirely on your phone, running the full pipeline from §25.6: global develop in order, at least two eye-directing local adjustments, a deliberate crop, and a correct export for one chosen destination. Save it into your Portfolio folder as the finished version, labeled 25-mobile-edit, and keep your original RAW and the unedited file beside it.

Why this image belongs, and the experiment it sets up. A portfolio is not just captures — it's finished photographs, and finishing is half the craft. This entry proves you can take a file all the way to delivery with nothing but the device in your pocket. But it's also a deliberate experiment for later: when you reach the digital darkroom on a desktop (Chapter 26), you will re-edit this same RAW on a big screen with a mouse, and compare the two finished versions. Keep notes now on every adjustment you made on the phone, so the comparison is real. You may be surprised how close the mobile edit gets — and exactly where (fine local masking, subtle color, judging sharpness) the big screen pulls ahead.

The curation note. Set this finished mobile edit beside the raw capture it came from and ask the portfolio question: does the edit reveal the photograph that was latent in the file, or does it impose something that wasn't earned in the capture? The strongest edits feel inevitable — the picture the negative was always going to become. That's the standard this entry holds itself to.

Summary

This chapter turned the phone into a complete darkroom and walked the full pipeline from a flat RAW to a published image. Reference-grade recap:

• A phone is a darkroom, not a compromise — the operations and decisions are identical to a desktop's; only the screen size and input method differ. There are four kinds of app: the camera (capture), the developer (your darkroom — where you live), the specialist (one job done well), and the publisher (the social platform, which silently re-edits what you upload). Choose one developer that does three things: accepts RAW, offers true local adjustments, and saves your own presets.
• Develop in a fixed order (Figure 25.2): white balance → overall exposure → recover highlights/shadows → contrast/curve → presence (texture/clarity/dehaze) → color (vibrance, then HSL) → then local + crop. Two laws: global before local, tone before color. Mobile RAW (ProRAW / DNG) is flat on purpose — that flatness is latitude, recoverable detail the JPEG already threw away.
• Local adjustments direct the eye. Four selection tools: radial (a subject/face), linear/graduated (skies, top-to-bottom changes — the digital graduated ND), brush (irregular shapes, freehand), and auto/AI masks (sky/subject/skin — verify the edges). Always zoom in to brush and feather the mask so the edit is invisible. Brighten the subject and gently darken the rest; the eye goes to bright and sharp.
• Presets give a set a shared look in one tap — but a preset sets style, not exposure. Apply it, then hand-finish each image's brightness. Build your own from edits you love (the start of a personal style); bought packs are at most an adaptable starting point, never a finished result. Aim for consistency, not sameness — a through-line, not a uniform.
• Export is a real decision, set per destination. Three things must be right: aspect ratio (crop it yourself so the platform doesn't — 3:2 prints, 4:5 portrait feed, 1:1 square, 9:16 vertical, 16:9 wide), resolution (~2,000–2,560 px long edge for web/social — over-large uploads look worse; full resolution for print), and output sharpening (a separate final pass — modest for screen, stronger for print, more for matte than glossy). Keep the RAW and the non-destructive edit as your master; the exported JPEG is a delivery copy.
• The whole pipeline runs on the phone: capture (RAW) → import → global develop in order → local adjustments → crop → save preset → export per platform → publish (knowing the platform re-edits). The Portfolio Checkpoint is one full run-through, kept beside its original for a desktop comparison in Chapter 26.

Spaced Review

Test yourself on earlier chapters without scrolling back:

1. (Chapter 22) Why would you choose to shoot a phone photo as RAW (ProRAW / DNG) instead of a normal JPEG, and what is the trade-off you accept for doing so?
2. (Chapter 3) When you set "overall exposure" in step 2 of the develop order, you watch the histogram. What is the histogram showing you, and what specifically are you looking for at its right-hand wall?
3. (Chapter 22 / 3) A friend says "I'll just fix the white balance later, so I don't need to think about the color of the light when I shoot." Using what you know about RAW and white balance, why is that mostly true for color temperature but not a license to ignore light when shooting?

What's Next

You have now finished a photograph end to end on a phone — which means you've quietly done a complete RAW develop, even if the small screen and the four-step order made it feel casual. Part VI takes that same process onto the big screen and goes deep. Chapter 26 opens the digital darkroom proper: the RAW file as exposed film, the histogram as your guide, the full global-develop pass, non-destructive editing and the catalog, and a repeatable develop order you'll recognize because you just did its mobile version here. We'll re-develop images with the precision a large display and a mouse allow — and you'll bring that Chapter 25 mobile edit along to compare. The performance you gave on the phone was real. Now we walk into the full studio and learn to give it on the largest, most controlled instrument there is.