717 Gigapixel Image of Rembrandt's Nightwatch

What's a good way of showing extremely high resolution images like this?

I did a few absolutely spectacular renders some years ago of a buddhabrot fractal, I don't remember the resolution but probably at least 100k x 100k, but after weeks of rendering I couldn't show it to anyone. I could only view it piecewise myself, as it didn't fit in RAM.

It's been a bit of a white whale for me.

I also have a high-res animated 4D rotation render that's half a dozen Gb, but can't be streamed online because compression algorithms absolutely massacre the details, and nobody wants to download files that big.

I did a bit of looking around at 4k matrix hardware, and it's pricey. There's probably someone making 8k by now, so it's just a matter of paying the high cost. Or get 1:16 1080p or something.

Other than that, 4k HDR TVs are cheap. Obviously 4k is too few, but at least you can make it 75" for under $1000...

As far as animations go, ffmpeg can work miracles.

Ipad has a nice high red and bright screen I suppose.

There's https://en.wikipedia.org/wiki/Deep_Zoom for example.

> A DZI has two parts: a DZI file (with either a .dzi or .xml extension) and a subdirectory of image folders. Each folder in the image subdirectory is labeled with its level of resolution. Higher numbers correspond to a higher resolution level;[6] inside each folder are the image tiles corresponding to that level of resolution, numbered consecutively in columns from top left to bottom right.

I don't think you quite understand the resolution of these images. If you were to arrange a 25x25 grid of 4K displays, perhaps. But that's like the size of an apartment building. And the whole point is that there is mesmerizing detail even close up. Zooming out doesn't do it justice.

Yeah, something like that is what I've been looking for.

This is what this site uses: https://openseadragon.github.io/

Apart from that needing to be a matrix of over 1200 4k TVs or over 300 8k TVs the problem here is opening and viewing the image not displaying it in full all at once. ffmpeg would run into the same RAM issues, the only approach to viewing such images is to split the image up into separate pieces and make multiple scale levels then feed it into a viewer that understands which pieces at which scale to load.