starred/flyimg

Fork 0

mirror of https://github.com/flyimg/flyimg.git synced 2026-04-25 01:35:56 +03:00

[GH-ISSUE #514] Cropping Image Changes Transparent Background To Solid Color #794

New issue

Closed

opened 2026-03-15 15:30:52 +03:00 by kerem · 10 comments

kerem commented

2026-03-15 15:30:52 +03:00

Owner

Originally created by @Jim-Webfox on GitHub (Sep 26, 2024).
Original GitHub issue: https://github.com/flyimg/flyimg/issues/514

Originally assigned to: @sadok-f on GitHub.

When taking an image with a transparent background, after resizing, cropping and setting output to png, a solid background is added to the image, it is no longer transparent.

Failing Result
https://demo.flyimg.io/upload/w_100,h_50,c_1,o_png/https://brandslogos.com/wp-content/uploads/images/large/laravel-logo-1.png

The image should maintain its transparent background.

Originally created by @Jim-Webfox on GitHub (Sep 26, 2024). Original GitHub issue: https://github.com/flyimg/flyimg/issues/514 Originally assigned to: @sadok-f on GitHub. When taking an image with a transparent background, after resizing, cropping and setting output to png, a solid background is added to the image, it is no longer transparent. Failing Result https://demo.flyimg.io/upload/w_100,h_50,c_1,o_png/https://brandslogos.com/wp-content/uploads/images/large/laravel-logo-1.png The image should maintain its transparent background. ![image](https://github.com/user-attachments/assets/76a14def-e6a9-40bd-862f-530be970849b)

kerem

2026-03-15 15:30:52 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-15 15:31:08 +03:00

Author

Owner

@sadok-f commented on GitHub (Sep 26, 2024):

Hi @Jim-Webfox ,
Thank you for opening this issue!

Yes, it seems the crop option adds a black background to the generated image.
I'll check it and I'll keep you updated.

@sadok-f commented on GitHub (Sep 26, 2024): Hi @Jim-Webfox , Thank you for opening this issue! Yes, it seems the crop option adds a black background to the generated image. I'll check it and I'll keep you updated.

kerem commented

2026-03-15 15:31:13 +03:00

Author

Owner

@sadok-f commented on GitHub (Sep 26, 2024):

@Jim-Webfox can you try again? I've deployed a new version with a potential fix.
since we're using the extent option to match the desired size given, we need to add -background none to remove the added background (black in your case).

@sadok-f commented on GitHub (Sep 26, 2024): @Jim-Webfox can you try again? I've deployed a new version with a potential fix. since we're using the `extent` option to match the desired size given, we need to add `-background none` to remove the added background (black in your case).

kerem commented

2026-03-15 15:31:18 +03:00

Author

Owner

@Jim-Webfox commented on GitHub (Sep 26, 2024):

@sadok-f Thanks for jumping on this so quickly!

It appears that its still happening. The link I provided in the initial issue still shows this, unless its using an old version of flyimg on the demo site?

@Jim-Webfox commented on GitHub (Sep 26, 2024): @sadok-f Thanks for jumping on this so quickly! It appears that its still happening. The link I provided in the initial issue still shows this, unless its using an old version of flyimg on the demo site?

kerem commented

2026-03-15 15:31:23 +03:00

Author

Owner

@sadok-f commented on GitHub (Sep 26, 2024):

Actually if you add the refresh option you'll get a new generated image rf_1 and the older image should be replaced by the new one, which is not the case here.
I need to look into this issue as well

@sadok-f commented on GitHub (Sep 26, 2024): Actually if you add the refresh option you'll get a new generated image `rf_1` and the older image should be replaced by the new one, which is not the case here. I need to look into this issue as well

kerem commented

2026-03-15 15:31:28 +03:00

Author

Owner

@Jim-Webfox commented on GitHub (Sep 26, 2024):

Ah good to know in future!

@Jim-Webfox commented on GitHub (Sep 26, 2024): Ah good to know in future!

kerem commented

2026-03-15 15:31:34 +03:00

Author

Owner

@sadok-f commented on GitHub (Sep 26, 2024):

I think I know what is happening, its not a bug.

Recently we started running the demo page on a docker swarm cluster, where the nodes are not sharing the cache nor the generated images folders.

So the rf_1 option should hit all of the nodes to get the refreshed generated image.

@sadok-f commented on GitHub (Sep 26, 2024): I think I know what is happening, its not a bug. Recently we started running the demo page on a docker swarm cluster, where the nodes are not sharing the cache nor the generated images folders. So the rf_1 option should hit all of the nodes to get the refreshed generated image.

kerem commented

2026-03-15 15:31:39 +03:00

Author

Owner

@Jim-Webfox commented on GitHub (Sep 26, 2024):

It Works!

https://demo.flyimg.io/upload/w_100,h_50,c_1,r_1,o_png/https://brandslogos.com/wp-content/uploads/images/large/laravel-logo-1.png

@Jim-Webfox commented on GitHub (Sep 26, 2024): It Works! https://demo.flyimg.io/upload/w_100,h_50,c_1,r_1,o_png/https://brandslogos.com/wp-content/uploads/images/large/laravel-logo-1.png

kerem commented

2026-03-15 15:31:44 +03:00

Author

Owner

@Jim-Webfox commented on GitHub (Sep 26, 2024):

Oh its rf_1 not r_1?

@Jim-Webfox commented on GitHub (Sep 26, 2024): Oh its rf_1 not r_1?

kerem commented

2026-03-15 15:31:49 +03:00

Author

Owner

@Jim-Webfox commented on GitHub (Sep 26, 2024):

ah still works

https://demo.flyimg.io/upload/w_100,h_50,c_1,rf_1,o_png/https://brandslogos.com/wp-content/uploads/images/large/laravel-logo-1.png

@Jim-Webfox commented on GitHub (Sep 26, 2024): ah still works https://demo.flyimg.io/upload/w_100,h_50,c_1,rf_1,o_png/https://brandslogos.com/wp-content/uploads/images/large/laravel-logo-1.png

kerem commented

2026-03-15 15:31:54 +03:00

Author

Owner

@Jim-Webfox commented on GitHub (Sep 26, 2024):

Im happy, if your happy also we can close this issue.

Thank you

@Jim-Webfox commented on GitHub (Sep 26, 2024): Im happy, if your happy also we can close this issue. Thank you