The browser first reads the image dimensions to show an immediate estimate. On upload, the server validates the file type, size, content, and dimensions, then binds the stored image record to the signed-in account. Before generation, the server verifies that the stored image record belongs to the current user. Server-stored dimensions are authoritative for output validation and billing; browser values are not trusted for charging.
The accepted file is stored through the site’s existing image workflow and passed through the configured processing service to create the enlarged result. Task state and output references use the existing account, storage, and history flow. This page does not claim that processing stays inside the browser or promise an unimplemented deletion schedule.
Credits are checked and charged by the server before processing. Existing failure handling is responsible for the matching refund path; retrying should not silently create a second charge for the same failed task.