사진을 JPG/PNG/WebP로 저장에 대한 리뷰
사진을 JPG/PNG/WebP로 저장 제작자: D7OM
리뷰 56개
- 5점 만점에 1점Firefox 사용자 17682403 님, 5일 전I saw the prompt requesting clipboard access and instantly removed it.
개발자 답글
6일 전에 게시됨Fair concern, permission prompts should never be silent surprises. Fully on me for not flagging it in the changelog.
Context: v1.3.0 added a "Copy image to clipboard" context-menu item (commit 2f9a5ec, P) to close issue #4. The
extension is open-source so the full diff is public. The actual clipboard code only writes an image — it never reads:
// src/offscreen/offscreen.js
const clipboardItem = new ClipboardItem({ [mimeType]: blob });
await navigator.clipboard.write([clipboardItem]);
Search the repo for clipboard.read or readText, you won't find a single call. The clipboardRead permission in the manifest was a mistake on my part (copy-pasted
alongside clipboardWrite) and was never used by any code path.
Since the feature is also unreliable on Firefox and is making people reasonably uneasy, I'm removing it entirely in the next release, both the feature and both clipboard permissions. The next version will ask for strictly fewer permissions than before. Sorry for the scare.개발자 답글
6일 전에 게시됨Fair concern, permission prompts should never be silent surprises. Fully on me for not flagging it in the changelog.
Context: v1.3.0 added a "Copy image to clipboard" context-menu item (commit 2f9a5ec, P) to close issue #4. The
extension is open-source so the full diff is public. The actual clipboard code only writes an image — it never reads:
// src/offscreen/offscreen.js
const clipboardItem = new ClipboardItem({ [mimeType]: blob });
await navigator.clipboard.write([clipboardItem]);
Search the repo for clipboard.read or readText, you won't find a single call. The clipboardRead permission in the manifest was a mistake on my part (copy-pasted
alongside clipboardWrite) and was never used by any code path.
Since the feature is also unreliable on Firefox and is making people reasonably uneasy, I'm removing it entirely in the next release, both the feature and both clipboard permissions. The next version will ask for strictly fewer permissions than before. Sorry for the scare.개발자 답글
6일 전에 게시됨Fair concern, permission prompts should never be silent surprises. Fully on me for not flagging it in the changelog.
Context: v1.3.0 added a "Copy image to clipboard" context-menu item (commit 2f9a5ec, P) to close issue #4. The
extension is open-source so the full diff is public. The actual clipboard code only writes an image — it never reads:
// src/offscreen/offscreen.js
const clipboardItem = new ClipboardItem({ [mimeType]: blob });
await navigator.clipboard.write([clipboardItem]);
Search the repo for clipboard.read or readText, you won't find a single call. The clipboardRead permission in the manifest was a mistake on my part (copy-pasted
alongside clipboardWrite) and was never used by any code path.
Since the feature is also unreliable on Firefox and is making people reasonably uneasy, I'm removing it entirely in the next release, both the feature and both clipboard permissions. The next version will ask for strictly fewer permissions than before. Sorry for the scare.- 5점 만점에 5점Julian Hill 님, 17일 전
- This add-on used to work. It used to actually download the files as the type you select. As of the last time I updated it, now it downloads them as whatever they are but just changes the file extension to the one you chose. For those unaware, that doesn't provide ANY of the benefits various file types would have. The big PNGs will still be just as big, the jpgs will still have artifacting, and the webps will still not function in many programs.
Literally all you had to do was make no changes to the add-on and it would have stayed good. wth man개발자 답글
한 달 전에 게시됨Hey, thanks for the report, you were right, it was broken. Just pushed a fix, update the extension and it should properly convert the files again. Sorry about that! - Been using this for a long time and its been great. Saves me a lot of time and keeps my workflow smooth.
However, I m facing an issue on two different devices. Even though I’ve set the default format to JPG, some images still download as PNG. If I open the extension settings and reselect JPG and save or reset the settings.. it works again, but after some time.. the same problem returns. I have set JPG as default and disabled the “view in store” option. - 5점 만점에 5점Firefox 사용자 19726559 님, 3달 전The fact you need this for basic functions in 2026 is embarrassing for Firefox/Chrome but thank goodness it exists.
- 5점 만점에 3점Venombeyond 님, 3달 전
- 5점 만점에 4점JollyOldFecker 님, 4달 전Great extension does exactly what it is meant to.
A great addition would be the option to select the save location. - 5점 만점에 3점Firefox 사용자 11735070 님, 4달 전
- 5점 만점에 5점Firefox 사용자 18253430 님, 4달 전
- 5점 만점에 5점Seychelles 님, 4달 전
- Works as described. You can save images that are otherwise in webp to jpg or png. It converts the image type and saves it to your download folder.
My only complaint is it doesn't ask you where you want to save or name your image file. That would be a major plus. Otherwise this extension works wonders개발자 답글
5달 전에 게시됨Thanks for the feedback! Unfortunately, browser extensions can't prompt users to choose where to save files or rename them - they can only save directly to the Downloads folder. This is a limitation of how extensions work, not something I can change. I wish I could add this feature, but it's not technically possible ATM. - 5점 만점에 5점Darwin4Ever 님, 5달 전It would be great (handier) if the Context-menu item would be "Save Image as Type" instead "Save image as" (which is also the name of the regular Save Image). "Save Image as Type" is also how it's identified in Chrome and mentioned in the "How to use". Installed version : 1.1.4
Because the Icon is White, it is not visible in the Context-Menu which is White too. Better would be to use the version as used at the top of the Addon-page in the Store개발자 답글
5달 전에 게시됨Thanks for the feedback! I'll fix both the menu name and the white icon issue asap just busy with work at the moment. Appreciate it!