"Error: Input buffer contains unsupported image format" for some remote images
See original GitHub issuevar resizer = sharp().resize( 300, 300 ).withoutEnlargement().max().toFile( 'public/img_thumbs/' + thumb_name, ( err, info ) =>
{
console.log( err );
});
request( url ).pipe( resizer );
Any idea why I’m getting “Error: Input buffer contains unsupported image format” for remote images like these?
I realize that maybe it’s more of a request module issue but I can’t figure out how to fix it specifically with sharp, besides the request response.headers[‘content-type’] returns correctly “image/jpeg”.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Sharp Error: Input buffer contains unsupported image format
I found the solution. const getImage = (req, res, next) => { const w = parseInt(req.params.w) const readStream = s3 .
Read more >Input buffer contains unsupported image format - Help
I have a problem with generating features and there is this Error: Input buffer contains unsupported image format. My Images are in jpg ......
Read more >Error: Input buffer contains unsupported image format
The error about the unsupported image format is referring to the fact that the words you are adding to the training data aren't...
Read more >Error: Input buffer contains unsupported image format ...
Coding example for the question Error: Input buffer contains unsupported image format when trying to use Next JS next-optimize-image-node.js.
Read more >Error "gatsby-plugin-manifest" Input file contains ...
I'm getting an unsupported image error when trying to deploy my Gatsby site to Netlify. The error is from the gatsby-plugin-manifest, see screenshot...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@pig-cop Could you share how you actually solved it? I’m having the same issue.
I solved it and it was the craziest thing! Those url strings, coming from html input forms, had url encoded ampersands!