Why Aspects

Open your layers panel and look at what you actually did today. For a lot of designers the honest answer is: cropped something to a ratio, dropped a screenshot into a phone, exported at a size somebody asked for. Then closed the file.

The tool is enormous. The job is small.

Photoshop is thirty five years of accumulated capability. Frequency separation, channel masking, camera raw, smart objects, actions, droplets, video timelines, 3D that came and went. It is a genuinely great program and almost nobody uses more than a corner of it.

That is not a criticism of the people using it. It is what happens when one application becomes the default answer to every question involving pixels. You learned it at school or at your first job, it was already open, and so the small daily jobs went there too. Cropping a hero image to 4:5 for Instagram is not a Photoshop problem. It just became one, because Photoshop was where you already were.

You are renting all of it, forever.

A subscription does not know which parts you use. It bills the same whether you spent the month retouching a campaign or resizing four screenshots for a deck. It bills during the months you did not open it. It bills after you stop freelancing, until you remember to cancel.

And the arithmetic runs one way. Every year you keep working is another year of payments, and at no point do you own anything. Stop paying and the files stay on your disk while the thing that opens them does not.

Aspects is the small job, bought once.

Aspects does one part of the work: getting finished things ready to publish. Capture a live website, including a deterministic scrolling video of it. Frame an image or a clip at any ratio. Crop without a frame. Cut video. Put a design into a photographic mockup you imported from a PSD, or a screenshot into a real device. Build an animation from a strip of stills.

Seven tools, each with a small number of dials, each exporting a file you can hand to somebody. That is the whole application. It is not trying to become the place you spend your day.

It costs $19. Not a year. Once. It keeps working when your card expires, when you go freelance, when you stop freelancing, and when you do not open it for eight months.

The only recurring thing is optional, and it is not the app.

There is a subscription, and it is worth being precise about what it buys, because this is the part people are right to be suspicious of.

It buys the cloud: your exports and folders synced to your account, available on the iPhone and iPad app, shareable with people you work with. That is a service with a running cost, so it has a running price.

Everything the Mac app does on your own machine is yours with the single payment. Rendering, exporting, every tool, every format. If you never sign in, the app never asks. If you subscribe and later stop, the app does not degrade into a viewer. Local editing and export keep working. The cloud switches off. That is the deal, and it is enforced in the code rather than promised in a footer: the app holds your last known entitlement, works offline for a month without reaching the server, and falls back to owning the app rather than to owning nothing.

What that actually changes.

Three things, and none of them is really about money.

You stop calculating. There is no monthly reminder to ask yourself whether you used it enough this month to justify it. A tool you have bought is a tool you reach for without doing arithmetic first.

You get something proportionate. A five second job in a program with two hundred panels is a five second job surrounded by two hundred panels. Small work goes faster in a small tool, and most of the friction was never the work.

You keep it. Whatever happens to us, the copy on your disk keeps opening and keeps exporting. That is what buying something is supposed to mean.

When you should keep Photoshop.

If your work is image making, keep it. Aspects does not retouch, does not paint, does not mask hair against a sky, does not do composites or colour grading or anything that involves making the picture rather than preparing it. It reads a PSD to import a mockup scene and that is the extent of the overlap.

The question is not which one wins. It is whether the small jobs need to keep happening inside the big program. For most people, most days, they do not.