Jump to content

Recommended Posts

Hi all,

Affinity Photo doesn't pixelate (Filter > Distort > Pixelate) images the same way other programs do. AP seems to pick the color of one pixel and uses it for the large pixel, while other tools usually use the average color of the overwritten pixels. In my opinion the result in Affinity Photo looks quite ugly, especially on faces where the result is usually asymetric.

Here an example: Original, Actual Affinity Photo result, Expected result from other programs.


Share this post

Link to post
Share on other sites

I don't really agree that it's uglier since I prefer the high contrast colours for better readability of the shapes. The filter is pretty excellent for pixel art where readability is super important. Would find it a lot easier to design a character with the high contrast colour palette than the blurier one.

That said, having any alternative pixelate algorithm certainly wouldn't be bad either. 

Share this post

Link to post
Share on other sites

The difference is merely that one was internally scaled down without anti-aliasing, and the other with anti-aliasing.

One issue with the pixelate filter is that it creates decimal pixels at the borders, which I dislike. Which is why I tend to avoid that method and prefer a basic scale down move.

Scaling down without and with anti-aliasing results in:


Scale down with nearest neighbour (which does not apply any anti-aliasing) or any of the other resampling algorithms for a softer anti-aliased result. Then scale up either result without anti-aliasing (nearest neighbour) to its original size. (This will introduce non-square non-precise blown-up pixels unless done in decimal steps - or use Resize Pixel Art Document)

That is true pixelation without those ugly half-pixels at the borders.

PS be VERY careful when resizing a document in Photo: it allows for non-decimal values, again resulting in weird decimal pixels at the borders when scaling down to a low resolution. Turning on pixel snapping, force pixel alignment, etc. doesn't seem to prevent this from occurring, which is buggy behaviour in my book. The only option is to use pixel values that result in decimal values for  width and height.

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.