Editing aircraft photos: your workflow from RAW to export

A good day at the fence often ends with 500 shots on the card – and with the question of how to turn them into the ten pictures you really want to show. If you want to edit aircraft photos, you rarely fail because of a slider, but almost always because of the order: you start developing at the first picture and give up at the fiftieth. This guide shows you a routine from RAW to export that also works after a long spotting day, and explains what matters with white fuselages, blue sky and shimmering asphalt.

Editing aircraft photos: the short answer

A resilient workflow has seven stations: import and backup, culling, basic development, straightening and cropping, noise and sharpness, export, archive. Each station reduces the number of pictures for the next. You only edit the few pictures that remain at the end individually and thoroughly – everything else runs through ratings and batch processing.

The software is secondary. Whether Lightroom Classic, Capture One, the free open-source programs darktable and RawTherapee or your camera manufacturer’s software: what matters is that the program works non-destructively. Your changes are saved as instructions, the original RAW file stays unchanged, and only at export does the program create a new picture.

Why RAW is especially worthwhile for aircraft

Aircraft subjects are a contrast challenge for any camera. Many airlines go for white fuselages – the article Why aircraft are painted white explains why. Against a bright sky and in full sun, these surfaces blow out quickly, while the underside of the fuselage and wings lies in shadow. Dark liveries, as on some special liveries, reverse the problem.

A RAW file stores the sensor data with significantly more tonal gradations than a JPEG. That gives you three concrete advantages:

• Highlight headroom: Slightly overexposed fuselage areas can often still be recovered as long as the sensor wasn’t fully saturated.
• Free white balance: You correct artificial light on the apron, evening sun or gray November weather without loss of quality.
• Clean shadows: A dark fuselage underside on approach can be brightened without color streaks or coarse noise appearing right away.

Which camera settings give you the best starting point is covered in the guide on camera settings for plane spotting. In short: better to expose slightly tighter so the highlights are preserved – you recover the shadows more easily in development.

Step 1: import, naming and backup

Import is the moment when a flood of files becomes an archive – or doesn’t. You take care of three things here right away:

• Folder structure: One folder per day and airport, for example 2026-10-15_EDDF. The airport’s ICAO code is short and unambiguous; what is behind the codes is explained in the article IATA and ICAO codes.
• Metadata: You assign the copyright notice and basic keywords like airport and spot right when importing. You enter registration and type only for the keepers after culling – how to read a registration reliably is shown in Understanding aircraft registrations.
• Backup: The 3-2-1 rule has proved its worth: three copies of your data on two different storage media, one of them in a different location. A copy on the same hard drive as the original doesn’t count.

You format the memory card only when both copies exist and you’ve opened a few pictures from the backup as a spot check – and then in the camera, not on the computer.

Step 2: culling in two passes

The biggest time sink in editing is developing pictures that you end up deleting anyway. So you cull before development, in two clearly separated rounds.

First pass – just yes or no. Full-screen view, no zoom, one to two seconds per picture. What obviously doesn’t work gets thrown out:

• Aircraft cut off: nose, tail, wingtips or engines missing
• Fence, light mast or another aircraft obstructs important parts
• strong backlight with a dark silhouette when you wanted a documentary shot
• clearly shaky or clearly focused in the wrong place

Second pass – the best of each subject. Now you compare series side by side and zoom to 100 percent. Look for sharp cockpit windows and a legible registration, for heat haze, which smears details over long distances, and for the aircraft’s position in the frame. Usually one or two shots remain per flyby.

Step 3: basic development

In basic development, you work from global to local and from technical to creative. Pictures with the same lighting situation – same spot, same time of day – you edit once and transfer the settings to the whole group.

The typical problem cases at the airport and the matching remedies at a glance:

Problem in the picture	Cause	Approach in development
Fuselage glows white with no structure	highlights overexposed	lower highlights and whites, pull exposure back slightly
Underside almost black	high sun, shot from below at an angle	lift shadows, brighten locally with a mask
Sky milky gray	haze or high cloud	use dehaze very sparingly, set black point
Picture looks bluish	shadow or overcast sky	color temperature slightly warmer
Color fringes at the edges	lens chromatic aberration	lens correction and fringe removal
Sliders maxed out, picture still bad	backlight or heat haze	cull instead of rescue

If your pictures are regularly taken against the sun, the article on backlight aircraft photography is worth a look – sometimes a deliberate silhouette is the better solution than a forced side view. For gray days, there are tricks of their own, collected in the guide Plane spotting in bad weather.

Step 4: straightening and cropping

Nothing gives away an unedited spotter photo faster than a tilted horizon. Photo databases watch for it, and on Instagram, too, a tilting terminal looks restless.

• Choose the right reference: Building edges, masts, the tower or the horizon are true verticals and horizontals. The fuselage is not – on takeoff the aircraft lifts its nose, on approach it sits slightly crooked in the wind.
• Aircraft without a ground reference: For shots against a blue sky, there is no reference. Here you straighten to the natural attitude so that a climb or turn stays believable.
• Room in the direction of flight: Leave a bit more space in front of the nose than behind the tail. The aircraft then looks as if it were flying into the picture.
• Don’t crop too tight: Wingtips, engines and tail fin need some air to the edge of the frame. With long-haul jets like the Airbus A350-900 or the Boeing 777-300ER, that happens faster than you’d think.
• Set the aspect ratio: For side views of aircraft, wide formats like 3:2 or 16:9 work well. For portrait format on social networks, you’d rather crop a separate variant.

If you have to take away a lot of picture area when cropping, the focal length was too short. How to avoid that next time is in the guide on the right focal length for plane spotting.

Step 5: sensor spots, noise and sharpness

Remove sensor spots. An evenly blue sky at a small aperture like f/8 or f/11 makes dust on the sensor visible as dark dots. Many programs have a view that makes such spots visible. Removing them is pure maintenance and doesn’t change the image content.

Reduce noise. On evening flights, gray weather or night shots, the ISO rises quickly. Some current RAW converters offer AI-assisted noise reduction, which often preserves more detail than classic sliders. Such functions generally work directly on the RAW data, so you apply them early in the routine. Classic noise reduction you dose sparingly: too much makes fuselage rivets, lettering and registrations waxy soft.

Sharpen for output. The most important rule: you sharpen for the size at which the picture is shown. A picture downsized to 1,280 pixels needs different sharpening than the full resolution. Many export dialogs therefore offer output sharpening for screen or print. When checking, look for bright halos at the fuselage edges against the sky – such halos are the typical sign of oversharpening and can lead to rejection at photo databases.

Step 6: export for every destination

An export is always just a derivative of your RAW file with its development settings. Create a separate export preset for each destination, and this step takes seconds.

Destination	Format and color space	Size (long edge)	Note
Social media and messengers	JPEG, sRGB	about 1,080 to 2,048 px	the platform recompresses, so don’t output too small
Photo database	JPEG, sRGB	per the platform’s requirements	check aspect ratio, file size and editing rules beforehand
Own website or portfolio	JPEG or WebP, sRGB	2,000 to 2,500 px	enough for large screens, but still loads fast
Print and photo book	JPEG or TIFF at full resolution	full resolution	agree on the color space with the print service

Photo databases have the strictest rules. AirNav Radar, for example, states in its upload guidelines (as of October 2026) a resolution between 768 and 4,000 pixels per edge, an aspect ratio of at most 1.9 to 1, a maximum of 4 MB per file and landscape format only. Added to that are content criteria: sharp edges, no large blown-out or black areas, a level horizon, an unobtrusive watermark and preserved EXIF data. Other platforms set their own limits and sometimes check every picture by hand. Read the current rules before you create the export preset.

Export metadata deliberately. The copyright notice should be in the exported picture. GPS coordinates, on the other hand, reveal your exact location – think about whether you want to include them.

How much editing is allowed?

Spotter photos are judged by a different standard than free photographic art. Anyone documenting which aircraft was where and when may optimize the picture, but not falsify it.

Especially with rare visitors and special liveries, the temptation is great to rescue an obstructed picture. For databases and your own documentation, though, only the picture as it was taken counts.

Step 7: archive and documentation

After export, the RAW files stay in the archive with their development settings. You can delete the rejected shots from the first pass after a grace period – the main thing is that you decide deliberately and not out of lack of space. For the keepers, enter registration, type and airline at the latest now. That way you can find a picture of a specific Lufthansa aircraft or an Emirates A380 in seconds even years later. How to turn that into a real sighting logbook is described in the guide Documenting sightings.

What to keep in mind

• Calibrated screen: A monitor that is too bright or has a color cast makes your pictures look too dark or wrong everywhere else. Calibration, or at least a neutral brightness setting, helps.
• Before-and-after comparison: Switch to the original view regularly. After half an hour of editing, the eye gets used to exaggerated saturation.
• Maintain presets: A base setting per camera and typical lighting situation – such as “Terminal Düsseldorf afternoon” – saves you the first steps on every visit.
• Don’t rescue every picture: If all sliders are maxed out, the shot was the problem. Learn from it for the next day at the spot, such as at the Düsseldorf observation deck or the Munich Airport visitors’ hill.
• Check the backup: A backup you’ve never test-restored is only a hope.

Conclusion

Editing aircraft photos is above all a question of order. If you back up first, then cull in two rounds and only then develop, you need a fraction of the time for a full spotting day. In development itself, the highlights take priority with aircraft: rescue white fuselages, open shadows moderately, don’t overdo colors. Added to that are a cleanly aligned horizon, sharpening matched to the output size and export presets for every destination. If you also write registration and type into the metadata, your picture folder gradually becomes an archive you enjoy browsing. If you’re just starting out, you’ll find the basics in the guide Plane spotting for beginners.