Why is the upload limited to 512 × 512 pixels?
Client-side super-resolution uses meaningful memory, GPU capacity and time. The strict limit helps avoid an unresponsive browser, especially with software WebGL or lower-power devices.
LOCAL AI EXPERIMENT
Swin2SR lightweight runs the default local 2× enhancement in a dedicated worker. Input is strictly limited to 512 × 512 pixels.
Experimental comparison: ESRGAN Slim
Optionally run ESRGAN Slim on the same ≤ 512 × 512 image. It uses 256px tiled inference with 10px padding, so you can compare texture, text and processing time against the default Swin2SR path.
The Swin2SR model loads only after you start. Processing stays in a dedicated worker and may be slow on lower-power devices.
SOURCE · ≤ 512 PX
Choose a small image to test
SWIN2SR · 2× RESULT
The 2× result appears here
ESRGAN SLIM EXPERIMENTAL COMPARISON
256px tilesRun ESRGAN Slim to compare its 2× result
This experimental clarity-upscaling tool runs Transformers.js + Swin2SR lightweight in a dedicated worker for local 2× inference. Inputs are strictly limited to 512 × 512 pixels to avoid long GPU and memory use; an optional ESRGAN Slim 256-pixel tiled result is available for comparison. Visual enhancement is not real detail recovery, lossless enlargement or image restoration.
BEST FOR
People who want to test 2× visual enhancement on a small image and understand its device and invented-detail limits.
Choose a small image no larger than 512 × 512 pixels
Start the local Swin2SR 2× inference in a worker
Optionally run the ESRGAN Slim comparison for texture, text and processing time
Inspect text, faces and repeated textures for invented detail, then download PNG if suitable and keep the source image
Client-side super-resolution uses meaningful memory, GPU capacity and time. The strict limit helps avoid an unresponsive browser, especially with software WebGL or lower-power devices.
No. It is model-driven visual enhancement and can create plausible-looking texture or detail that did not exist in the source.
Yes. Cancel resets the local model session and restores page controls. On some devices the underlying GPU work can take a moment to release fully.
GlobalCoreHub runs the core Experimental AI 2× Upscaler workflow in the current browser. Tool input is not uploaded to the GlobalCoreHub application server; any local saving described on this page stays in the current browser until its site data is cleared.