Art & Design · head-to-head
DummyImage vs Rijksmuseum
DummyImage generates placeholder images on the fly from a simple URL pattern — width, height, background/text color, and format (PNG, GIF, or JPG) are all encoded in the path — with no signup or key. A live GET against the real host returned a genuine PNG carrying Access-Control-Allow-Origin: *, resolving cors unknown -> yes and reconfirming auth None.
The Rijksmuseum has replaced its old key-gated REST collection API with a free, fully keyless Linked Open Data service: a Linked Art-based Search API at data.rijksmuseum.nl/search/collection and a Persistent Identifier Resolver at id.rijksmuseum.nl, both returning JSON-LD. A live GET against the real search endpoint returned 1,463 genuine matching results for a Rembrandt query with Access-Control-Allow-Origin: *, and its own docs explicitly state no API key is needed — correcting the stored url off its retired /object-metadata/api/ path (now a 404), auth API Key -> None, and cors unknown -> yes.
| DummyImage | Rijksmuseum | |
|---|---|---|
| Authentication | None | None |
| Pricing | free | free |
| Formats | PNG, GIF, JPG | JSON-LD |
| CORS | yes | yes |
| HTTPS | Yes | Yes |
DummyImage supports 3 response formats, while Rijksmuseum offers fewer — pick DummyImage for more integration flexibility.