Hi, it seems that Shadertoy has changed something on their website. They were down recently, and it looks like they’ve added a human verification step.
Importing from Shadertoy now results in this error: Network Error: “201”.
Hmm. That’s unlikely to change in the ISF editor, but I’ll make note of it to the team. ShaderToy is most likely experiencing a massive amount of data scraping for AI vibecoding, and I’m assuming their aim is to protect the coders from the problem.
this is what I was thinking too.
Hope you’ll find a solution with shadertoy :)
If changes to the ISF Editor are unlikely, perhaps a local proxy service could serve a shader’s pasted or locally saved tabs in a format compatible with the Editor’s existing Shadertoy importer.
This would allow users to manually copy or save a shader’s tab(s) from Shadertoy and have the proxy simulate the expected Shadertoy network responses locally.
An extended solution would also encompass GLSLSandbox shaders, for which I get “Error: downloaded data is empty”. for every one I’ve tried to import.
In the meantime I just tried asking Claude AI to convert a copy/pasted Shadertoy shader (single tab) to ISF. I then copy/pasted Claude’s code into the ISF Editor. It worked first time, and subsequent requested tweaks almost always worked too. Only one compilation error in the ISF editor in the whole session, and that was fixed on the first attempt.
1 Like
No chance to get back the import functions ? @ProjectileObjects
Unlikely. If shadertoy is trying to prevent bots from scraping their code, they’ll most likely keep changing their security protocols to combat this. As other have mentioned the LLM tool sets can handle these conversions for now.