Home/ Questions/Q 6073273
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T10:15:12+00:00

I’m using Google’s Custom Search API to dynamically provide web search results. I very

  • 0

I’m using Google’s Custom Search API to dynamically provide web search results. I very intensely searched the API’s docs and could not find anything that states it grants you access to Google’s site image previews, which happen to be stored as base64 encodes.

I want to be able to provide image previews for sites for each of the urls that the Google web search API returns. Keep in mind that I do not want these images to be thumbnails, but rather large images. My question is what is the best way to go about doing this, in terms of both efficiency and cost, in both the short and long term.

One option would be to crawl the web and generate and store the images myself. However this is way beyond my technical ability, and plus storing all of these images would be too expensive.

The other option would be to dynamically fetch the images right after Google’s API returns the search results. However where/how I fetch the images is another question.

Would there be a low cost way of me generating the images myself? Or would the best solution be to use some sort of site thumbnailing service that does this for me? Would this be fast enough? Would it be too expensive? Would the service provide the image in the correct size for me? If not, how could I change the size of the image?

I’d really appreciate answers that are comprehensive and for any code examples to be in ruby using rails.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    So as you pointed out in your question, there are two approaches that I can see to your issue:

    1. Use an external service to render and host the images.
    2. Render and host the images yourself.

    I’m no expert in field, but my Googling has so far only returned services that allow you to generate thumbnails and not full-size screenshots (like the few mentioned here). If there are hosted services out there that will do this for you, I wasn’t able to find them easily.

    So, that leaves #2. For this, my first instinct was to look for a ruby library that could generate an image from a webpage, which quickly led me to IMGKit (there may be others, but this one looked clean and simple). With this library, you can easily pass in a URL and it will use the webkit engine to generate a screenshot of the page for you. From there, I would save it to wherever your assets are stored (like Amazon S3) using a file attachment gem like Paperclip or CarrierWave (railscast). Store your attachment with a field recording the original URL you passed to IMGKit from WSAPI (Web Search API) so that you can compare against it on subsequent searches and use the cached version instead of re-rendering the preview. You can also use the created_at field for your attachment model to throw in some “if older than x days, refresh the image” type logic. Lastly, I’d put this all in a background job using something like resque (railscast) so that the user isn’t blocked when waiting for screenshots to render. Pass the array of returned URLs from WSAPI to background workers in resque that will generate the images via IMGKit–saving them to S3 via paperclip/carrierwave, basically. All of these projects are well-documented, and the Railscasts will walk you through the basics of the resque and carrierwave gems.

    I haven’t crunched the numbers, but you can against hosting the images yourself on S3 versus any other external provider of web thumbnail generation. Of course, doing it yourself gives you full control over how the image looks (quality, format, etc.), whereas most of the services I’ve come across only offer a small thumbnail, so there’s something to be said for that. If you don’t cache the images from previous searches, then your costs reduces even further, since you’ll always be rendering the images on the fly. However I suspect that this won’t scale very well, as you may end up paying a lot more for server power (for IMGKit and image processing) and bandwidth (for external requests to fetch the source HTML for IMGKit). I’d be sure to include some metrics in your project to attach some exact numbers to the kind of requests you’re dealing with to help determine what the subsequent costs would be.

    Anywho, that would be my high-level approach. I hope it helps some.

    • 0