We've given the account dashboard a refresh! You'll now find a dedicated announcements pane to keep you in the loop, plus a handy Help & Tips section to make navigating even easier. Announcements and News posts are separate from eachother.

We've given the account dashboard a refresh! You'll now find a dedicated announcements pane to keep you in the loop, plus a handy Help & Tips section to make navigating even easier. Announcements and...

During a routine backend review, we uncovered a bug in our stats system—specifically, the Premium user count was incorrectly including non-activated accounts in the stats on the homepage and generator pages.

We’ve since fixed the issue, and the counter now reflects accurate, real-time data.

During a routine backend review, we uncovered a bug in our stats system—specifically, the Premium user count was incorrectly including non-activated accounts in the stats on the homepage and generat...

We have recently identified a compatibility issue affecting users accessing our website via Apple devices (iOS and macOS). While our platform includes mobile-responsive design and functions as intended on Windows and Android systems, we have observed intermittent problems for Apple users, including:

Incomplete page loading
Errors in form submissions
Delayed or failed script execution


The root cause lies in architectural differences between Apple’s WebKit-based browsers (Safari, Chrome for iOS) and Chromium/Blink-based browsers (Chrome, Edge, Brave) commonly used on Windows and Android. Key factors include:

1. Stricter Privacy and Tracking Policies – Apple enforces Intelligent Tracking Prevention (ITP), which restricts third-party cookies and cross-site scripting. This can interrupt session handling, authentication flows, and form validation logic that rely on certain client-side storage mechanisms.

2. Differences in JavaScript Engine and Rendering – Safari uses JavaScriptCore, while Chromium uses V8. Subtle discrepancies in ES6+ feature support, CSS flexbox/grid rendering, and WebAPI implementations can cause layout shifts or script failures, particularly with polyfills or legacy code.

3. HTTP/2 and TLS Handling – Apple devices prioritize different cipher suites and may reject certain certificate configurations or compression protocols, leading to connection timeouts or resource loading failures.

4. Service Worker and Cache Behavior – Safari imposes stricter limits on service worker cache size and lifecycle, which can break offline asset loading or progressive web app (PWA) functionality.

These discrepancies do not indicate a flaw in our site’s mobile support, but rather reflect the fragmented browser landscape—particularly Apple’s unique interpretation of web standards.


We acknowledge this issue and intend to resolve it in a future site update. However, we must be transparent: our development team currently operates exclusively within Windows and Android environments, and none of our engineers use Apple hardware for daily testing. This creates a practical limitation in reproducing and debugging Safari-specific behavior in real time.

To bridge this gap, we are:

Acquiring remote device testing access (e.g., BrowserStack, Sauce Labs) for macOS/iOS simulation.
Reviewing our front-end build process to adopt broader cross-browser polyfills and fallbacks.
Planning a dedicated compatibility sprint in Q3 2026, with a target fix by September.

In the interim, we recommend Apple users try alternative browsers (e.g., Firefox for iOS) or temporarily access the site via a Windows/Android device if available. We sincerely apologize for the inconvenience and appreciate your patience as we work toward a fully inclusive user experience.

For further assistance, please contact our support team at support@gtauploads.com

We have recently identified a compatibility issue affecting users accessing our website via Apple devices (iOS and macOS). While our platform includes mobile-responsive design and functions as intende...