By continuing to use our services on or after May 25, 2018, you indicate your agreement with the new terms and policies that are effective as of that date. There will be no change to the functionality of the imgix service, but we do hope that you will find these updated terms beneficial. If you have any feedback, please feel free to contact us at email@example.com.
imgix has an ongoing commitment to provide our customers with industry-leading security, so we want to inform you about a change that we will make to the imgix CDN to continue that commitment.
imgix enables you to deliver your images to your users using either HTTP or HTTPS by leveraging the worldwide, high-performance imgix CDN. HTTPS delivery is available with every imgix source, at no additional cost and without additional setup, because we strongly believe that allowing our customers to securely deliver their content is an essential part of the value of the imgix service. To follow the best currently available security practices, we periodically evaluate the imgix CDN’s configuration parameters. During our most recent evaluation, and due to changes to PCI requirements, we will be retiring the availability of older TLS protocols and a legacy encryption cipher for all customers of the imgix CDN.
Effective today, the imgix CDN will no longer support connections utilizing the TLS v1.0 or TLS v1.1 protocols. TLS v1.2 will continue to be supported. Additionally, we will no longer support the 3DES cipher. All other current ciphers will continue to be supported.
imgix has launched support for IPv6 connectivity on the imgix CDN. It is available to all imgix customers immediately.
Why IPv6 matters for your images
As more devices join the global Internet community, especially in newly emerging markets, the availability of IPv4 addresses has largely been exhausted. Over time, this means that more and more end-user traffic to IPv4-only services must be routed through IPv6-to-IPv4 gateway services, such as carrier grade NAT devices operated by ISPs and mobile carriers. This allows new devices to access every site on the Internet, but performance may suffer as a result.
IPv6 adoption has grown slowly, but has recently begun to accelerate. This traffic now accounts for over 10% of global Internet traffic, and considerably more when only mobile device networks are considered. Recent studies have shown that native IPv6 connectivity can have a significant positive performance impact on content delivery.
By offering native IPv6 connectivity to all of our customers, we are eliminating this bottleneck. All end-user devices on the Internet will be able to utilize their preferred path, whether IPv4 or IPv6, to connect to the imgix CDN and obtain your images as fast as possible.
No setup required
IPv6 connectivity is automatically enabled for all imgix CDN customers. No configuration is required for your imgix Source and we handle DNS for you. IPv6 connectivity to origin servers is not currently offered. Our CDN pricing remains the same: one flat per-gigabyte rate for each of our 50+ worldwide edge nodes, with no additional charges for the number or types of requests.
Business is global, and ensuring fast page load speed is a critical task for every company when competing for customers’ attention. This is especially true with increased mobile-first usage in many parts of the world.
To expand your reach, we’ve added four new edge nodes. Two in India—Mumbai and Chennai—and one in Santiago, Chile will greatly improve our image load times throughout Asia and South America. In addition, we've expanded our North American capacity with a new node in Columbus, Ohio. We’re looking forward to even more in the new year so we can continue to bring your images to customers faster, no matter where they are.
Last Wednesday, the first CodePen SF meetup happened, sponsored by imgix. There was no major headline speaker or program that was planned months in advance. The speakers and attendees were anyone interested in learning more about front-end development or design, some with no technical background. The program consisted of any brave person willing to share out a Pen they found or created themselves. You can check out our recap email and pictures from the event.
There were mistakes. There were laughs. It was genuine and human. And I’m so glad we did it.
It’s easy to find meetups where the perfect product or advice is provided, but it’s harder to find one that allows anyone—expert or not–to share something, tell a story, fumble a bit, and receive a round of applause at the end.
You see, I don’t know how to code. I only have a basic understanding of a few languages from online tutorials and playing around on CodePen. So when I went to the CSS Dev Conf back in October of this year, I truly felt like a fish out of water. I was the imposter syndrome incarnate.
At the end of the conference though, a CodePen Show & Tell was put on by Chris Coyier himself (the co-founder of the site) and for the first time, I felt like I should be there. The environment was welcoming and nonjudgmental and bits of code here and there started to make sense after seeing it being manipulated live. There was a glimmer of understanding on my part and I wanted others who aren’t developers to have it too and the idea for starting CodePen SF was born.
If this sounds like you in some way, I hope you’ll join us at our next event in February. imgix is proud to have sponsored this first event, and we'll see you there too.
I’ve run into a lot of varied challenges while building websites and apps over the last two decades. Every project I’ve tackled has presented unique problems, but one consistent issue has been figuring out the best way to deal with images. Every part of the image workflow is difficult; Image files are bulky, and there are lots of formats to deal with. This results in a lot of time spent processing images, and a lot of storage space required for derivatives.
imgix’s dynamic image workflow abstracts those complexities. A traditional image flow might look something like this:
A user uploads an image. For this example, let’s say it’s a profile photo.
A server running ImageMagick or a similar program creates derivative versions of the uploaded image. For something like a profile photo that’s used in many contexts throughout a site or app, the number of derivatives for each upload can be quite high. I’ve seen derivative counts in the dozens before!
The original image and generated derivatives are uploaded from the image server to a permanent storage location, e.g. Amazon S3.
With imgix, the process is inverted. Instead of generating all derivatives up front, they’re requested and generated on the fly. Each derivative can be created easily by changing the appended parameters in the image URL. This allows developers a lot of additional flexibility, letting them solve some long-standing problems in new ways.