For nearly three decades, serious image editing meant one thing: a heavy desktop application, a licence, and a machine powerful enough to run it. That arrangement is quietly dissolving. Creative work is moving into the browser — not as a compromise, but because collaboration, versioning and access from anywhere turned out to matter more than raw feature count for a large share of the work people actually do.
This guide covers both halves of that story. First, how image editing actually works — layers, masks, colour, resolution, non-destructive editing — because understanding the model makes every tool easier to learn. Then, why creative software moved to the web, what became possible in the browser, and how to choose sensibly between desktop and web tools for real projects.
What you will learn
- The core concepts behind every image editor, explained once and transferable
- Raster versus vector, and why choosing wrongly causes most beginner frustration
- Non-destructive editing and why professionals work that way
- Colour, resolution and file formats without the folklore
- What made browser-based creative tools genuinely viable
- How to choose between desktop and web tools for a given project
- What an image editor actually is
- Raster and vector
- Layers: the central idea
- Selections and masks
- Non-destructive editing
- Colour, properly understood
- Resolution and sizing
- File formats and when to use each
- Retouching and compositing in practice
- Why creative tools moved to the browser
- What the browser made possible
- Desktop or web: choosing per project
- Where generative tools fit
- Twelve mistakes that cost hours
- A practical workflow, start to finish
- Frequently asked questions
1. What an image editor actually is
Underneath the interface, a photo editor is a program that manipulates a grid of coloured dots. Every operation — brightening, blurring, cropping, adjusting colour — is arithmetic performed on those numbers. Understanding this removes most of the mystery and explains behaviour that otherwise seems arbitrary.
A pixel stores an intensity for red, green and blue, plus often an alpha value representing opacity. Brightening an image adds to those values. Increasing contrast pushes values away from the middle. Blurring replaces each pixel with an average of its neighbours. Sharpening does the reverse, exaggerating differences between neighbours.
This explains a fundamental limitation. Information that has been discarded cannot be recovered. If a photograph's sky is pure white because it was overexposed, those pixels contain no detail — there is nothing to bring back. "Enhance" as portrayed in television is fiction; what modern tools actually do is generate plausible new detail, which is a different operation with different implications.
2. Raster and vector
Two ways of representing an image, and choosing wrongly is the single most common source of frustration for people learning design tools.
| Raster | Vector | |
|---|---|---|
| Stores | A grid of pixels | Mathematical shapes and paths |
| Scaling up | Becomes soft or blocky | Perfectly sharp at any size |
| Best for | Photographs, textures, painted artwork | Logos, icons, illustrations, type |
| File size | Grows with dimensions | Depends on complexity, not size |
| Editing | Pixel-level control | Shapes remain editable forever |
The practical rule: if it will ever need to appear at more than one size, make it vector. A logo drawn as pixels at the size you first needed will be unusable on a billboard and blurry on a high-resolution display. A logo drawn as vectors works at every size from a favicon to a building.
Photographs are inherently raster, because a camera sensor is a grid of light sensors. There is no vector representation of a photograph, which is why photo editing and illustration remain distinct disciplines with distinct tools.
3. Layers: the central idea
Layers are the concept that separates casual editing from real editing, and every capable tool has them. A layer is a transparent sheet stacked above the image. Paint on it and you affect only that sheet; the original stays untouched underneath.
Three properties turn this into a working method:
- Order. Layers stack, and higher ones obscure lower ones where they are opaque. Rearranging changes the composition instantly.
- Opacity. Each layer's contribution can be dialled up or down without repainting anything.
- Blend mode. How a layer combines with what is beneath. Normal covers; multiply darkens; screen lightens; overlay increases contrast. These are simple mathematical operations between the two layers' pixel values, and knowing that makes choosing between them far less mysterious.
Blend modes explain a great deal of professional technique. Painting shadows on a layer set to multiply darkens without changing colour. Painting highlights on screen brightens the same way. Because these are separate layers, the effect can be reduced, masked or removed entirely at any point — which is the whole reason to work this way.
The discipline that pays off most is layer hygiene: name your layers, group related ones, and keep the structure comprehensible. A file with sixty layers called "Layer 47 copy 3" is unusable by anyone including your future self, and creative work is revisited far more often than anyone expects.
4. Selections and masks
A selection defines which pixels an operation affects. A mask is a saved, editable selection attached to a layer. The distinction matters: selections are temporary, masks are permanent and adjustable.
A mask is itself a greyscale image where white means fully visible, black means fully hidden, and grey means partially transparent. This is why painting on a mask with a soft brush produces gradual transitions — you are painting shades of grey into the visibility map.
The professional habit is simple and consequential: mask instead of erasing. Erasing destroys pixels permanently. Masking hides them, and hiding is reversible. Paint white on the mask and the content returns. Every non-destructive workflow rests on this substitution.
Modern selection tools have improved dramatically, with subject detection and edge refinement handling cases that once took an hour of manual work. What has not changed is that difficult edges — hair, fur, motion blur, semi-transparent fabric — still require judgement, and that the quality of a composite is usually decided at its edges.
5. Non-destructive editing
The principle underneath every professional workflow: never permanently alter the original data. Every edit should be an adjustable instruction layered on top rather than a change baked in.
Four techniques implement it:
- Adjustment layers apply colour and tonal changes as separate layers rather than to the pixels. Change your mind about the exposure a week later, and it is one slider.
- Masks instead of erasing, as described above.
- Smart or linked objects that keep the original data intact while allowing transforms, so scaling down and back up does not degrade quality.
- Duplicating before destructive operations where the tool offers no alternative — a habit worth building.
The cost is larger files and slightly more setup. The benefit is that revision is cheap, and creative work is almost entirely revision. Clients change their minds, and a file where the change means adjusting one layer rather than starting over is the difference between an afternoon and a morning.
6. Colour, properly understood
Colour causes more confusion than any other topic, and three ideas resolve most of it.
Colour models describe how colour is represented. Screens use red, green and blue light added together; more of everything means brighter. Print uses cyan, magenta, yellow and black inks subtracting light; more of everything means darker. Because the two work in opposite directions, some colours achievable on screen simply cannot be printed — which is why a vivid design sometimes prints disappointingly, and why converting late in the process produces unpleasant surprises.
Colour spaces define exactly which colours the numbers mean. The same numeric value can represent noticeably different colours in different spaces. A wide space contains more vivid colours but is not displayed correctly by software that ignores the embedded profile — which is why an image can look correct in an editor and washed out in a browser.
Bit depth determines how many gradations exist between values. Eight bits per channel is standard for final images and adequate for viewing. Sixteen bits gives far more intermediate values, which matters during editing: heavy tonal adjustment on an eight-bit image produces banding in gradients, because there are not enough intermediate values to represent the smooth transition. Edit in the higher depth and export in the lower one.
The practical guidance for most people: work in a standard space unless you have a colour-managed workflow end to end, edit at higher bit depth when making significant tonal changes, and always soft-proof before committing to print.
7. Resolution and sizing
Resolution generates persistent confusion because one number is doing two jobs.
Pixel dimensions are the actual amount of information — a 4000 by 3000 image contains twelve million pixels regardless of any other setting. Dots per inch is a printing instruction describing how densely those pixels should be laid down on paper. It has no effect whatsoever on screen display.
This is why "make it 300 DPI" is meaningless without a physical size. What matters for print is pixel dimensions divided by the intended physical size. An image 3000 pixels wide printed at ten inches yields 300 pixels per inch, which is appropriate for quality print. The same file printed at thirty inches yields 100, which will look soft.
For screens, only pixel dimensions matter — but modern displays pack more physical pixels into the same space, so an image intended to occupy a 400-pixel-wide slot should be supplied at two or three times that to appear sharp. Supplying images at exactly the layout size is why photographs look soft on high-resolution laptops and phones.
Enlarging beyond the original always involves invention. Traditional interpolation produces softness; machine-learning upscaling produces plausible invented detail, which is often better-looking and is genuinely fabricated. That distinction matters for anything evidential or documentary.
8. File formats and when to use each
| Format | Use for | Watch out for |
|---|---|---|
| JPEG | Photographs for web and general sharing | Lossy; quality degrades every time it is re-saved |
| PNG | Graphics with transparency, screenshots, flat colour | Large files for photographs |
| WebP / AVIF | Modern web delivery — smaller at equal quality | Support is now good but check your audience |
| SVG | Logos, icons, illustrations on the web | Vector only; sanitise files from untrusted sources |
| TIFF | Print production and archival masters | Very large files |
| Print delivery, multi-page documents | Embed fonts and check colour conversion | |
| Native project files | Work in progress with layers intact | Never the deliverable; always export a flat copy |
The most damaging habit is repeatedly editing and re-saving a JPEG. Each save discards information permanently, and after several rounds the degradation is clearly visible. Keep a lossless master, edit that, and export a JPEG each time you need to deliver one.
9. Retouching and compositing in practice
Two families of work with different disciplines.
Retouching improves an existing image. The order that works: fix distortion and crop first, correct exposure and contrast, then colour, then local adjustments, then blemish removal, then sharpening last — always last, because sharpening amplifies whatever is already there, including noise and compression artefacts.
The mark of good retouching is that it is not noticed. The most common failure is overdoing it: skin that has lost all texture, skies so saturated they look artificial, and shadows lifted so far the image looks flat. Working with adjustment layers helps here, because reducing an effect by a third is one slider rather than a redo.
Compositing combines several images into one. Three things determine whether it convinces the eye, and all three are about physical consistency rather than technique: light must come from the same direction with the same hardness, perspective and camera height must match, and colour temperature must agree. A technically perfect cut-out will still look wrong if the subject is lit from the left and the background from the right — and viewers detect that immediately without being able to say why.
10. Why creative tools moved to the browser
For years the browser was assumed incapable of serious creative work. Several changes removed that assumption, and it is worth knowing which, because they explain what browser tools can and cannot do.
The browser gained direct access to graphics hardware. Rendering and image operations that once required native code can now run on the graphics processor from within a web page, which closed most of the raw performance gap for typical editing operations.
Compiled code became runnable in the browser. Existing image-processing code written in systems languages can be compiled to run in a web page at close to native speed, which meant entire mature codebases could move rather than being rewritten.
Real-time collaboration was solved. The underlying techniques for merging simultaneous edits from several people without conflicts matured to the point where multiple designers editing one document became routine rather than experimental.
Storage and delivery moved anyway. Once files, versions and assets lived in cloud services, the local application was already the odd part of the workflow.
But the decisive factor was not technical. It was that collaboration turned out to matter more than features for most professional work. A tool where a designer, a product manager and an engineer can look at the same artboard, comment on it and see changes live eliminates an entire category of coordination overhead — and that is worth more to most teams than the deepest feature set.
11. What the browser made possible
- No installation or version mismatch. Everyone is on the current version, and a link opens the actual document rather than a screenshot of it.
- Real-time multi-user editing, with presence, comments and review threads attached to the work itself rather than to an email chain.
- Automatic version history. Every state recoverable, and named milestones for significant versions. This alone eliminates the folder full of files ending in "final-v3-revised".
- Sharing as a first-class action. A URL with defined permissions instead of a file that immediately becomes stale.
- Platform independence. The operating system stops being a constraint on who can participate.
- Extensibility through plugins running in the same environment, which has produced ecosystems that would be impractical to distribute as desktop installers.
The honest limitations remain. Very large files and extremely high-resolution print work still favour desktop applications. Colour management for professional print is more reliable natively. Deep hardware integration — graphics tablets with pressure and tilt, calibrated displays, camera tethering — works better outside the browser. And offline capability, while improving, is not equivalent.
12. Desktop or web: choosing per project
| If the project involves… | Lean towards |
|---|---|
| Interface design reviewed by a team | Web — collaboration dominates |
| High-resolution print production | Desktop — colour management and file size |
| Photo retouching at full sensor resolution | Desktop — performance and precision tooling |
| Quick edits, crops, exports | Web — faster to open than to install |
| Illustration with a graphics tablet | Desktop — pressure and tilt handling |
| Design systems shared across teams | Web — components, libraries, live updates |
| Work with sensitive material | Depends entirely on your data policy, not on features |
| Occasional use by non-specialists | Web — no licence, no installation, lower barrier |
Most professional workflows now mix both, and the practical friction is at the boundary. Keep masters in a lossless, layered format, agree where the source of truth for each asset lives, and be deliberate about which tool owns which stage. The chaos in mixed workflows comes almost entirely from ambiguity about which file is authoritative.
13. Where generative tools fit
Machine-learning features have become ordinary parts of image tools, and it helps to separate them by how much they invent.
Assistive features accelerate work you would do anyway: automatic subject selection, sky replacement masking, noise reduction, and content-aware removal of unwanted objects. These are reliable, save substantial time, and are uncontroversial.
Generative features invent new content: extending an image beyond its original frame, filling a region with plausible material, or producing an image from a description. These are genuinely capable and carry two considerations that assistive features do not. The output may not be usable commercially depending on the tool's training and licensing terms, which must be checked rather than assumed. And for anything documentary, journalistic or evidential, generated content is fabrication regardless of how convincing it looks.
The workflow that has emerged among professionals is generation for exploration and iteration, followed by conventional craft for the final result. Generative tools produce many options quickly, which is valuable at the stage where you are deciding what to make. They are less suited to the stage where precision and consistency matter, because they are difficult to direct exactly and produce slightly different results each time.
14. Twelve mistakes that cost hours
- Working raster when the asset needs to scale. A logo in pixels is a logo you will redraw.
- Erasing instead of masking. Destroys the option to change your mind.
- Editing a JPEG repeatedly. Compounding quality loss with every save.
- Unnamed layers. A file nobody, including you, can navigate in a month.
- Flattening too early. Every subsequent revision starts from scratch.
- Sharpening before other adjustments. Amplifies noise and artefacts you then have to fight.
- Ignoring colour space. Correct in the editor, wrong everywhere else.
- Confusing DPI with pixel dimensions. Delivering files that are soft in print.
- Exporting at exact layout size. Soft images on high-resolution displays.
- Compositing with mismatched light. Technically clean and immediately unconvincing.
- No master file. Only a flattened export survives, and revision means redoing the work.
- Over-retouching. Skin without texture and skies without credibility.
15. A practical workflow, start to finish
Concepts settle faster when attached to a real sequence. Consider a common brief: a product photograph that must appear on a website, in a printed brochure, and as a social post — three destinations with different requirements from one source image.
Start from the largest original you have. Camera raw where possible, because it retains far more tonal information than a compressed export and gives real latitude for exposure and white balance corrections. Everything downstream is derived from this master; the master itself is never overwritten.
Corrections before decisions. Straighten and correct lens distortion first, because both change the framing and doing them after cropping means cropping twice. Then set white balance, then overall exposure and contrast. These are global corrections that establish a neutral, accurate starting point — the point at which the image is right rather than interesting.
Build the edit in layers, not in the pixels. Convert to a layered working file. Exposure and colour adjustments go on adjustment layers. Dust and blemish removal goes on its own empty layer so it can be reduced or removed. Local brightening and darkening go on separate layers set to appropriate blend modes, each with a mask so the effect can be reshaped. At no point are the original pixels altered, which means every decision remains negotiable.
Cut out the product properly if the background must change. Selection tools will get most of the way; the quality of the result is decided at the edges. A slight contraction of the selection and a small feather usually removes the halo of background colour that otherwise gives a composite away. Save the selection as a mask so it can be refined rather than redone.
Now branch for each destination, and only now. For print, convert a duplicate to the print colour space, soft-proof it to see which colours cannot be reproduced, adjust the ones that shift badly, size it to the physical dimensions the printer specified, and export a flattened file with the profile embedded. For the website, size to the layout width multiplied by two for high-density screens, export in a modern compressed format at several widths, and check the file size against your performance budget. For social, crop to the platform's aspect ratio deliberately rather than letting the platform crop for you, because automatic cropping will find the least flattering framing available.
Sharpen per destination, last, at the final size. Sharpening is resolution-dependent: an amount that looks correct at print size will look crude on a small web image. This is why it is the final step in each branch rather than a step in the shared edit.
The whole sequence takes perhaps forty minutes and, more importantly, survives the client asking for the product to be slightly brighter three weeks later — which is a five-minute change rather than a restart, because nothing was ever baked in.
16. Frequently asked questions
Do I need to learn Photoshop specifically?
The concepts transfer far more than the interface does. Layers, masks, blend modes, adjustment layers, selections and colour spaces work the same way in every capable editor. Learn the concepts in whichever tool you have access to, and moving to another is a matter of finding where the menu items live rather than relearning the craft.
Are free tools good enough?
For most work, yes. Open-source raster and vector editors implement the full conceptual toolkit and are entirely capable for web graphics, retouching and illustration. Paid tools tend to win on refinement — better selection algorithms, smoother large-file performance, more polished professional print output — rather than on capability. Constraints are more likely to come from a specific studio requirement or a collaborator's file format than from the software itself.
What should I use for interface design?
A dedicated interface design tool rather than a photo editor. They are built around the things interface work needs: reusable components, layout constraints, consistent spacing, prototyping and developer hand-off. Using a photo editor for interface design is possible and consistently slower, because you are maintaining by hand what a purpose-built tool maintains automatically.
How do I hand images to developers properly?
Vector formats for logos and icons; modern compressed formats at several sizes for photographs; and always specify the intended display size so density can be handled correctly. Agree a naming convention, and provide the source file alongside the exports so regeneration does not require asking you. Most friction in hand-off comes from missing sizes and ambiguous naming rather than from anything technical.
Is browser-based editing safe for confidential material?
It depends on the provider's terms and your obligations, not on the technology. Check where data is stored, whether it is encrypted at rest, whether content may be used to improve the service, and what happens on account termination. Many organisations run web tools under an enterprise agreement that addresses these; others restrict sensitive work to local tools by policy. Answer this before adopting a tool, not after a project has started.
How do I stop my design looking amateurish?
Four things account for most of the difference: consistent spacing on a defined scale, a restrained type palette of two families at most, deliberate alignment so nothing sits slightly off, and sufficient contrast for text to be readable. None require artistic talent, and all four are checkable. Most work that reads as unprofessional is failing one of them rather than lacking creative flair.
Should I learn generative tools?
Yes, as an addition to craft rather than a substitute for it. They are genuinely useful for exploration, variation and removing tedious work. They are poor at precision, consistency and following an exact brief, which is where trained judgement remains necessary. The practitioners getting the most from them are the ones who already know what good looks like and can therefore direct and evaluate output quickly.
What is the one habit worth building first?
Non-destructive editing. Adjustment layers rather than direct changes, masks rather than erasing, and a layered master file kept separately from exports. It takes slightly longer the first time and saves hours on every revision — and revision is where the vast majority of creative time actually goes.
Key takeaways
- Understand the model, not the menus. Layers, masks and blend modes transfer between every tool.
- Choose raster or vector by whether it must scale. This single decision prevents most rework.
- Work non-destructively. Adjustment layers and masks make revision cheap, and revision is most of the job.
- Pixel dimensions matter; DPI is a print instruction. Confusing them is why files arrive soft.
- The browser won on collaboration, not features. Shared editing, versioning and links beat feature depth for team work.
- Generative tools explore; craft finishes. Use each for the stage it suits.
The tools will keep changing — they always have. What does not change is the underlying model: light stored as numbers, arranged in layers, revealed through masks, and adjusted by instructions you can always take back. Learn that once, and every new tool becomes a matter of finding the buttons.
Enjoyed this article?
Get more engineering insights from ELIVTECH — or talk to us about your project.
Get in touch