Resellers, stores that stock Nike and people building a lookbook often want a sharper copy of a nike.com product photo than "Save image as" gives them. Nike resizes every photo on the fly from a much larger upload, and the size is written into the image address, so you can ask for the big one.
Right-click the main photo on a product page and choose "Open image in new tab". The address looks like this:
https://static.nike.com/a/images/t_web_pdp_535_v2/f_auto,u_9ddf04c7-…,c_scale,fl_relative,w_1.0,h_1.0,fl_layer_apply/b7d9211c-…/AIR+FORCE+1+%2707.png
The part that starts with t_ is a size preset. f_auto lets the server pick the format, and Chrome gets AVIF. The u_… step lays the photo on Nike's light grey background. The long ID after it is the photo, and the name at the end is the product.
I fetched two product pages and one category page and read the pixel size of each copy from the file:
| Photo | On the page | Size preset removed |
|---|---|---|
| Air Force 1 '07, main photo | 1070×1338 px (t_web_pdp_535_v2) | 2880×3600 px |
| Club Fleece Pullover Hoodie, main photo | 1070×1338 px (t_web_pdp_535_v2) | 2880×3600 px |
| Tech Therma-FIT hoodie, tile on the men's hoodies page | 1184×1184 px at most (t_web_pw_592_v2), 318×318 px on a narrow screen | 3144×3144 px |
The mobile carousel on the same Air Force 1 page asks for t_web_pdp_936_v2, which came back at 1872×2340 px, and the colour chips next to it are 144×144 px.
t_… part and the slash after it, so the address goes straight from /a/images/ to f_auto,u_…. On a category page tile, delete every step between /a/images/ and the u_ step; they only set the size and format.For the file Nike uploaded, delete everything between /a/images/ and the photo ID: https://static.nike.com/a/images/b7d9211c-…/AIR+FORCE+1+%2707.png. That gave me a PNG at the same 2880×3600 px. On the Air Force 1 the background in that PNG is transparent, and on the hoodie it is solid. These PNGs are large: about 3.5 MB for the shoe and about 10 MB for the hoodie.
Chrome saves the edited address as AVIF because of f_auto. The WebP to JPG guide covers free ways to save it as a JPG, and they work for AVIF too.
PixLasso has a rule for static.nike.com. With Full-size originals on, which is the default, it removes the size steps and keeps the background step, which is what Method 1 does by hand. I ran its URL code on the addresses above and got the 2880×3600 px photos from the product pages and the 3144×3144 px photo from the category tile. On a category page that means one full-size photo per product in a single ZIP.
The free version saves 30 images per batch, and each press after that saves the next batch. Pro saves all of them in one press and converts a whole batch to JPG; it is a single payment of US$9.99 until 31 December 2026, then US$14.99.
Both methods save only the photos the page shows you. A product page loads its gallery as you look at it, so scroll through the photos before you start PixLasso. I measured three products; other photos may have been uploaded at a different size. Some category tiles show a lifestyle photo with a different address, and I did not test those.
That depends on your agreement with Nike or your supplier. The photos belong to Nike. Check the terms before you put them on a marketplace or a store.
Adidas uses the same kind of image server on assets.adidas.com, and PixLasso has a rule for it too. This guide only measured nike.com.
Tested on nike.com on 11 November 2026: I fetched two public product pages and the men's hoodies page, downloaded each size of the photos and read the pixel size from the image header, then ran PixLasso's URL code on the same addresses. Written by the developer of PixLasso; the first method needs no extension.