#Retina resolution calculator free

#Retina resolution calculator free

If not then you’ll want to upload and images manually with a free JavaScript library such as Retina.js. If you’re not as concerned with load times then just go with the largest resolution for all your images. These are much trickier and should either be uploaded at the highest resolution possible or updated with JavaScript. These queries check pixel density and load different background images for those devices(also adjusting the background size).ĬSS is generally the simplest way to handle images, but can’t be used for in-post images. The alternative method would be to load different CSS files based on JavaScript checks or backend server checks.īut perhaps the best way to handle CSS is with a CSS retina media query. It doesn’t hurt to have an over-optimized image in CSS if you don’t mind the extended load times. This is often the quickest way to check retina images because they can work on all devices, even non-retina devices. The simplest way to handle custom backgrounds is with retina background images using the background size property. I personally prefer CSS, but I recommend trying both to see what you prefer. Some images are better as JPGs and some websites are better with CSS vs JS retina checks. The goal is to decide file types and browser checks on a case-by-case basis. Plus SVG is not useful for detailed images like photographs since it’s really a vector filetype.īut SVGs have more room for custom animation which displays crisply at all resolutions. We don't have long to wait to find out who is right, who is adaptable, and which third-party developers will make the smart business decisions around the launch of the new hardware.The only difficulty is designing SVGs from scratch and learning to export them properly, which can be more convoluted than just using PNGs or JPEGs. We're about to see a lot more on our iOS devices. The actual resolution is important, but the thinking behind how the resolution is addressed by app developers, web designers, and others, is perhaps more important given the impact the iPhone 6 will have in the digital space. They may be waiting to see what the new screen resolutions are before committing development costs to graphical assists or doing a final polish on the UI. The very smart developers will already have their own application frameworks set up to work with points rather than pixels, and to adapt automatically with different screen sizes and screen resolutions. The smart iOS developers will have been working with the beta releases of iOS 8 since WWDC this year to have apps ready to go at the launch of the iPhone 6 range. This would be so sweet, I’d wager Apple comes up with a new marketing name for it: super-retina or something. At that point it would be difficult for most of us to perceive individual pixels from any viewing distance, not just from typical practical viewing distance. At 461 pixels per inch, it would be a monster: I'm sure the marketing department will love to talk about the iPhone with the highest quality screen that Apple has ever delivered. The screen resolutions proposed by Gruber also introduces a '3x retina resolution' for the 5.5 inch iPhone Phablet. The recent beta releases of Xcode have allowed any resolution to be set manually, rather than the fixed options of the iOS range (which had been the case with previous releases of Xcode). This ties in with Apple's subtle indications from WWDC that developers should not consider the screen of an iOS device as having a fixed size or ratio. Using points reduces much of the work in scaling a UI to be usable on any screen. While these are different pixel sizes, it allows Apple to set recommended minimums for screen elements in terms of point size across all iOS devices, rather than different minimums for different form factors. If a developer codes an application to display a single point on the screen, this could be a single pixel on lower resolution devices (such as the current iPad mini), or four pixels in a 2x2 configuration on higher resolution screens. One key think to remember in Gruber's calculation, and all the speculation around the iPhone 6 screens, is that Apple has been making a conscious effort to push developers away from using pixels as a unit of measurement and move them towards points. Given those fixed values, and considering the value of 16:9 as a screen ratio, the sensible choice is above, although it's worth nothing that this goes against the current thinking that the 4.7 inch iPhone display will run at 1704 x 960 pixels. The first is the physical size of the screen, which has been taken as gospel and the second is the pixels per inch values that Apple has historically favoured across all their hardware, even those with different screen technologies. Underpinning the calculation are two key data points. It's harder to extrapolate screen resolutions than colors (image: )