Every TGP Script Ever Made: The Software That Powered the Adult Web

Every TGP Script Ever Made: A Complete Guide to the Software That Powered the Adult Web

Between 1997 and 2010, a handful of software scripts powered an empire. TGP (Thumbnail Gallery Post) sites generated billions of pageviews per month, supported thousands of operators, and drove the commercial adult internet. But none of it would have been possible without the scripts—the specialized content management systems built specifically for the unique demands of thumbnail gallery sites.

This is the definitive guide to every significant TGP script ever made: what they did, who built them, what they cost, and what happened to them. For anyone who lived through the TGP era, this is a walk down memory lane. For everyone else, it’s a look at the software archaeology of an industry that shaped the web as we know it.

The Big Five: Scripts That Defined the Industry

1. AutoGallery — The People’s Script

AutoGallery was, by sheer volume, the most widely deployed TGP script in history. Its secret? It was free. Released as open-source Perl, it could be installed on virtually any shared hosting account that supported CGI—which, in the late 1990s, was nearly all of them.

Key Features:

\n
• Automated gallery submission and approval system
\n
• Category management with unlimited depth
\n
• Basic thumbnail downloading and caching
\n
• Trade link management with ratio tracking
\n
• Template system for customizing output pages
\n
• Scheduled page rebuilding via cron
\n
• Blacklist system for blocking spam submissions
\n

AutoGallery’s greatest strength was also its greatest weakness: accessibility. Because anyone could install it, the quality of AutoGallery-powered TGPs varied enormously. The best operators customized it extensively, writing their own Perl modules and templates. The worst just installed it out of the box and wondered why their traffic numbers were anemic.

The script went through several major versions, with AutoGallery Pro and AutoGallery SQL adding database-backed storage and improved admin interfaces. But it always maintained its core philosophy: free, functional, and flexible enough for operators who were willing to get their hands dirty with code.

Legacy: AutoGallery democratized TGP operation. It lowered the barrier to entry so far that anyone with $5/month hosting could run a TGP. This created the massive ecosystem of tens of thousands of sites that made the traffic trading economy viable.

2. TGPX — The Gold Standard

If AutoGallery was the Honda Civic of TGP scripts, TGPX was the BMW. Built by the same developer (JMB Software), TGPX was the commercial, professional-grade version designed for serious operators who needed reliability, performance, and advanced features.

Key Features:

\n
• Advanced anti-cheat system detecting bots, autosurfers, and fake submissions
\n
• Sophisticated trade tracking with multi-level ratio management
\n
• Automated thumbnail downloading, resizing, and quality assessment
\n
• Gallery scanning that verified content actually existed before approving
\n
• Built-in skim management with per-sponsor rate configuration
\n
• Comprehensive statistics dashboard with historical trending
\n
• Template engine with conditional logic and variable substitution
\n
• Bulk gallery management tools for high-volume operations
\n
• IP-based geotargeting for sponsor rotation
\n
• Automated content quality scoring
\n

TGPX earned its reputation through reliability and attention to detail. While free scripts would occasionally corrupt data or miss submissions, TGPX was rock-solid. Its anti-cheat systems were particularly sophisticated—it could detect and block dozens of different cheating techniques that gallery submitters used to game the system.

The $149-$199 price tag was a serious investment for many operators, but it paid for itself quickly. Sites running TGPX consistently outperformed sites running free scripts, both in traffic quality and revenue generation. The professional admin interface alone saved hours per week compared to managing a site through flat-file configs.

Legacy: TGPX proved that professional tooling was worth paying for in the adult web space. It set the standard that every subsequent TGP script was measured against, and its feature set became the template for what a “real” TGP script should include.

3. Smart Thumbs — The Anti-Cheat Specialist

Smart Thumbs carved out its niche by focusing obsessively on traffic quality and anti-fraud measures. In an ecosystem where cheating was rampant—fake submissions, bot traffic, gallery stuffing, redirect chains—Smart Thumbs positioned itself as the script for operators who demanded clean, legitimate traffic.

Key Features:

\n
• Industry-leading anti-cheat detection engine
\n
• Real-time gallery content verification
\n
• Automated duplicate detection across submissions
\n
• Traffic quality scoring for trading partners
\n
• Advanced skim controls with per-category and per-partner rates
\n
• Detailed submitter reputation tracking
\n
• Intelligent thumbnail selection (choosing the “best” thumbnail from a gallery)
\n
• Automated category suggestions based on content analysis
\n

At $250, Smart Thumbs was more expensive than TGPX, and it justified the premium with its detection capabilities. The script could identify and block automated submission tools, detect recycled galleries being submitted under new URLs, and flag suspicious traffic patterns from trading partners. For operators who ran premium TGPs with high-value sponsor relationships, these features were invaluable.

The 19,000+ installation figure (often cited in their marketing) made Smart Thumbs one of the most commercially successful TGP scripts, though it never matched AutoGallery’s free-tier ubiquity or TGPX’s prestige positioning.

Legacy: Smart Thumbs pushed the entire industry toward better anti-fraud measures. Features it pioneered—like gallery content verification and submitter reputation scoring—eventually became standard in competing scripts.

4. TGS (Toxic Gallery System) — The Enterprise Option

At $1,200, TGS was the most expensive TGP script on the market by a wide margin. It targeted the top tier of TGP operators—the network owners running dozens of sites pulling millions of daily pageviews.

Key Features:

\n
• Military-grade anti-cheat system with real-time behavioral analysis
\n
• Multi-site management from a single admin interface
\n
• Distributed architecture supporting load balancing across servers
\n
• Advanced traffic routing with geotargeting and time-based rules
\n
• Custom C-compiled modules for performance-critical operations
\n
• API for integration with external trading and analytics systems
\n
• Automated content scanning with nudity detection
\n
• Enterprise reporting with export capabilities
\n

TGS justified its price with features that no other script offered. Its anti-cheat engine used behavioral analysis that was years ahead of the competition, detecting cheating patterns that other scripts missed entirely. The multi-site management capabilities allowed operators running 10, 20, or 50 TGPs to manage them all from a centralized dashboard.

The C-compiled performance modules were particularly notable. While other scripts ran purely as interpreted Perl, TGS offloaded performance-critical operations (like real-time click tracking and thumbnail processing) to compiled C code, giving it a significant speed advantage under high traffic loads.

Legacy: TGS proved that there was a market for enterprise-grade tooling in the adult web space, even at premium price points. Its multi-site management and API features foreshadowed the platform approach that modern CMS systems would eventually adopt.

5. Comus Thumbs — The Free PHP King

Comus Thumbs represented the next generation of TGP scripts, built from the ground up in PHP rather than Perl, with MySQL database backing instead of flat files. It arrived later than the Perl-era scripts but quickly gained a devoted following by offering commercial-grade features at no cost.

Key Features:

\n
• Traffic Booster AI — An algorithmic system that automatically optimized trade link placement based on traffic patterns, partner performance, and conversion data. This was genuinely revolutionary for its time.
\n
• PHP/MySQL architecture (more familiar to the growing PHP developer community)
\n
• AJAX-powered admin interface (cutting-edge for 2004-2005)
\n
• Built-in thumbnail generation with ImageMagick/GD integration
\n
• Automated gallery quality scoring
\n
• Flexible template system with PHP-based logic
\n
• Trade management with automated ratio balancing
\n
• Comprehensive skim management with detailed reporting
\n
• RSS feed generation for gallery distribution
\n
• SEO-friendly URL generation
\n

The Traffic Booster AI was Comus Thumbs’ killer feature. While other scripts required operators to manually adjust trade link placement and rotation, Comus Thumbs used algorithmic analysis to automatically determine optimal placement. It would analyze which trading partners sent the highest-quality traffic (measured by time on site, pages per visit, and conversion rates) and dynamically adjust link prominence accordingly.

By building on PHP/MySQL instead of Perl/flat files, Comus Thumbs also attracted a new generation of operators who were more comfortable with the LAMP stack. The AJAX admin interface—unusual for any web application in 2004—made day-to-day management significantly more efficient.

Legacy: Comus Thumbs bridged the gap between the Perl era and the PHP era. Its Traffic Booster AI concept—algorithmic optimization of traffic distribution—was ahead of its time and directly influenced the development of ComusThumbz, the modern platform that carries its DNA forward.

The Supporting Cast: Every Other TGP Script

Aardvark TGP

An early free alternative that gained traction before AutoGallery matured. Known for its simplicity and small footprint, Aardvark TGP was popular with operators on extremely limited hosting. Its feature set was basic—gallery submission, category management, simple trade tracking—but it worked reliably on shared hosting accounts with strict resource limits. Eventually overshadowed by AutoGallery’s more active development.

Celestial TGP

Celestial TGP positioned itself as a mid-tier commercial option between the free scripts and TGPX. It offered a clean admin interface, reasonable anti-cheat detection, and solid trade management at a lower price point than the premium scripts. Celestial developed a loyal user base among operators who wanted something better than free but couldn’t justify TGPX’s price. Its template system was particularly praised for flexibility.

FTGPS (Free TGP Script)

FTGPS was one of the first PHP-based TGP scripts to gain meaningful adoption. Released under the GPL, it attracted PHP developers who wanted to customize and extend a TGP script without learning Perl. While it never matched AutoGallery’s deployment numbers, FTGPS played an important role in proving that PHP was a viable platform for TGP software and encouraging the transition from Perl to PHP in the adult web development community.

X3 TGP Script

X3 arrived relatively late in the TGP era but brought modern PHP development practices to the table. It featured a clean, database-driven architecture, a responsive admin panel, and built-in SEO tools that reflected the growing importance of search engine traffic. X3 was popular among operators who were building new TGP sites during the tail end of the era and wanted something more modern than the aging Perl scripts.

TGPSoft

TGPSoft targeted the budget-conscious commercial operator. At $79-$129, it was the cheapest paid script with a meaningful feature set. It offered decent gallery management, basic trade tracking, and a functional admin interface. TGPSoft was never a top-tier script, but it filled an important niche for operators who wanted commercial support and regular updates without paying TGPX or Smart Thumbs prices.

FetchGals

FetchGals was a lightweight Perl script focused specifically on automated gallery downloading and thumbnail generation. Rather than being a full TGP management system, it specialized in the content acquisition side—fetching galleries from submission feeds, downloading and caching thumbnails, and organizing content for display. Many operators used FetchGals alongside another TGP script, using it as a content pipeline feeding into their primary system.

ZippedTGP

ZippedTGP took an unusual approach to content delivery: instead of linking to individual gallery pages, it offered downloadable ZIP archives of gallery images. This was particularly popular in the pre-broadband era when users wanted to download content for offline viewing rather than browsing individual pages on slow connections. The script managed gallery packaging, download tracking, and bandwidth management. As broadband became widespread, the download model lost relevance, and ZippedTGP faded.

RaTGP

RaTGP (often stylized as raTGP) was a community-driven open source project that aimed to build a modern TGP script through collaborative development. It featured a plugin architecture that allowed developers to extend functionality without modifying core code. While the concept was sound, the project suffered from inconsistent development and limited documentation. It gained a small but dedicated community of developer-operators who appreciated the extensibility.

LinksList

LinksList was technically a general-purpose link directory script rather than a TGP-specific tool, but it was widely adapted for TGP use in the early days. Before dedicated TGP scripts matured, many operators ran modified LinksList installations. It offered basic link categorization, submission forms, and simple page generation. Its flexibility meant it could be bent into a TGP-like shape, even though it wasn’t purpose-built for it. LinksList represents the “before times”—the period before the industry had standardized on purpose-built TGP software.

The Supporting Tools Ecosystem

TGP scripts didn’t operate in isolation. A rich ecosystem of supporting tools grew up around them:

Gallery Submitter Pro

The essential tool for content producers and sponsors who needed to submit galleries to hundreds of TGPs simultaneously. Gallery Submitter Pro maintained a database of TGP submission URLs and form formats, allowing users to prepare a gallery submission once and distribute it to hundreds of sites with a single click. It handled CAPTCHAs, different form formats, and submission rate limiting to avoid being flagged as spam. At its peak, Gallery Submitter Pro was used to submit millions of gallery links per day across the TGP ecosystem.

CJ Flash (Circle Jerk Flash)

Despite its name, CJ Flash was actually a legitimate traffic analysis tool. It monitored outgoing click patterns to detect whether trading partners were running circle jerk operations. By tracking how quickly visitors bounced back from partner sites and analyzing the referrer chains, CJ Flash could identify partners who weren’t delivering genuine traffic. It became an essential tool for operators who wanted to maintain clean trading relationships and avoid being associated with circle jerk networks.

TradePulse

TradePulse was a standalone traffic trading management system that worked alongside any TGP script. It provided more sophisticated trade tracking than most built-in systems offered, with features like multi-tier ratio management, automated partner evaluation, and predictive analytics that estimated how much traffic a potential new trading partner could deliver. Operators running multiple TGP sites found TradePulse invaluable for managing complex trading networks across all their properties.

NATS (Next-Generation Affiliate Tracking System)

While not TGP-specific, NATS by Too Much Media was the industry-standard affiliate tracking platform that many TGP sponsors used to track conversions from TGP traffic. NATS provided the crucial link between traffic and revenue—when a TGP visitor clicked through a skim redirect and eventually signed up for a paid site, NATS tracked that conversion and attributed it to the correct TGP operator. It was the most widely deployed affiliate tracking system in the adult industry and remains active today, having evolved far beyond its TGP-era origins.

The Hierarchy: Who Used What

By the mid-2000s, a clear hierarchy had emerged in the TGP script market:

Notable exception: Comus Thumbs operators frequently outearned operators on paid scripts, because its Traffic Booster AI actually delivered better traffic optimization than many commercial alternatives. Being free didn’t mean being inferior—it meant having a different business model.

What Happened to Each Script

The tube revolution of 2006-2010 didn’t just kill TGP sites—it killed the scripts that powered them. Here’s what happened to each:

\n
• AutoGallery: Development ceased around 2008. The website went dark. Thousands of installations continued running on autopilot for years, gradually accumulating broken gallery links and outdated templates.
\n
• TGPX: JMB Software continued development longer than most, eventually pivoting to offer tube site management features. The script is still technically available but receives minimal updates.
\n
• Smart Thumbs: Company dissolved around 2009. Website went offline. The 19,000+ installations gradually went dark.
\n
• TGS: Toxic Productions shifted focus to other adult web technologies. TGS stopped receiving updates around 2007.
\n
• Comus Thumbs: Evolved into ComusThumbz—the modern platform discussed below.
\n
• Celestial TGP: Disappeared around 2006-2007. No trace remains online.
\n
• FTGPS: Open source repository went inactive. Last meaningful commits around 2007.
\n
• X3: Developer moved to other projects around 2008.
\n
• TGPSoft: Website went offline around 2008.
\n
• FetchGals, ZippedTGP, RaTGP, LinksList: All faded into digital obscurity by 2005-2007.
\n

The pattern was remarkably consistent: as TGP traffic declined, script revenue (from new licenses, support contracts, and upgrades) declined in parallel. Developers couldn’t justify continuing to maintain software for a shrinking market. One by one, the lights went out.

ComusThumbz: The Evolutionary Successor

Of all the TGP scripts listed above, only one lineage survived and evolved into a modern platform: Comus Thumbs became ComusThumbz.

But ComusThumbz isn’t just Comus Thumbs with a new coat of paint. It’s a ground-up reimagination that takes the best ideas from the entire TGP script ecosystem and implements them for the modern era:

\n
• From AutoGallery: Accessibility and ease of deployment. ComusThumbz can be installed and configured without deep technical expertise, maintaining the low barrier to entry that made AutoGallery the most widely deployed TGP script.
\n
• From TGPX: Professional-grade reliability and comprehensive feature coverage. ComusThumbz offers the same depth of functionality that made TGPX the gold standard—90+ API endpoints, 49 controllers, comprehensive admin panel—all built on modern PHP 7.4+ with strict types.
\n
• From Smart Thumbs: Anti-cheat and quality control. ComusThumbz’s click tracking gateway monitors traffic quality, detects anomalies, and provides the same kind of traffic quality assurance that Smart Thumbs pioneered.
\n
• From TGS: Enterprise-scale architecture. Multi-CDN support (BunnyCDN, Wasabi, Backblaze, Cloudflare R2, and more), distributed video conversion across multiple servers, and a REST API designed for integration—the same enterprise thinking that justified TGS’s $1,200 price tag, now available in a modern framework.
\n
• From Comus Thumbs: Intelligent traffic optimization. The Traffic Booster AI concept lives on in ComusThumbz’s analytics and skim management system, which uses detailed traffic data to optimize monetization automatically.
\n

Beyond TGP: What ComusThumbz Added

While honoring its TGP heritage, ComusThumbz goes far beyond what any TGP script could do:

\n
• Video processing pipeline: FFmpeg-powered transcoding to HLS and MP4, with automated thumbnail extraction, preview clip generation, animated GIF creation, and contact sheet generation. This is the modern equivalent of thumbnail generation, but for streaming video.
\n
• Creator monetization: A complete creator economy system with tipping, subscriptions, pay-per-view content, and token transactions. No TGP script ever imagined this because the creator economy didn’t exist yet.
\n
• Live streaming: LiveKit WebRTC integration for live webcam streaming. Another capability that didn’t exist in the TGP era.
\n
• REST API: 90+ endpoints enabling mobile apps, third-party integrations, and headless architecture. TGP scripts generated static HTML pages; ComusThumbz serves dynamic content through a modern API.
\n
• Multi-language support: 25 languages out of the box. TGP scripts were English-only (or required manual translation of template files).
\n
• GDPR compliance: Built-in privacy controls, consent management, and data export capabilities. Legal compliance wasn’t even a consideration in the TGP era.
\n

The TGP script era produced remarkable software under remarkable constraints—Perl scripts running on shared hosting, managing millions of pageviews with flat-file databases and creative caching. The developers who built AutoGallery, TGPX, Smart Thumbs, TGS, and Comus Thumbs were pioneers who solved hard problems with limited tools.

ComusThumbz honors that legacy by carrying forward the core principles—traffic tracking, content aggregation, intelligent monetization, operator control—while building on the modern infrastructure those pioneers could only dream of. It’s not just a TGP script for the tube era. It’s the culmination of everything the TGP script ecosystem taught us about running adult content platforms.

The scripts may be gone, but the knowledge they embodied lives on.