Liquify tool stops working after changing brush size on iPad

[Vanessa Photography]

Hi everyone,

since the latest Photoshop for iPad update, I’ve been having a persistent issue with the Liquify tool. It works perfectly fine when I open it and use the default brush size (100) — but as soon as I change the brush size, the tool completely stops responding.

It doesn’t crash the app, but it just stops applying any distortion — no matter how I move my Apple Pencil or finger. If I reset the brush size back to 100, it still doesn’t work anymore until I restart Photoshop.

Here’s what I’ve already tried:

– Restarted the iPad

– Reinstalled Photoshop

– Cleared cache / checked storage

– Tried different files and formats (8-bit, 16-bit, different resolutions)

– Checked Pencil pressure and smoothing settings

Nothing fixed the issue. It happens every time the brush size is changed.

My setup:

– iPad Pro (M4)

– iPadOS (18.7.1)

– Photoshop for iPad (6.6.2)

– Apple Pencil Pro

Would really appreciate if the Adobe team could confirm whether this is a known issue and if a fix is in progress.

It’s one of my most-used tools, and it currently makes Liquify unusable for detailed retouching.

Thanks a lot for your time —

Vanessa

[Vanessa Photography]

Just updated to iPadOS 26.0.1 – unfortunately no improvement. Liquify still stops responding right after changing the brush size.

[Vanessa Photography]

Also updated Photoshop to 7.0  –  still not working.

[Vanessa Photography]

Update:

I noticed something interesting about the Liquify issue. When I change the brush size and zoom in very closely, I can actually see that the tool is still working — just extremely small.

It seems that after adjusting the brush size, Liquify automatically resets to a brush size of 1, no matter what size was selected.

When I switch to another tool and back to Liquify, the size value always shows 1.

So the tool doesn’t completely stop working — it just registers the wrong brush size after any adjustment, which makes it look like it’s not responding.

Thanks @Jim_Rick6879 for the suggestions — unfortunately they didn’t solve the issue, but I appreciate the help!

Hope this update helps the team identify what’s going on.