Camera Gear Site Spec Comparison Overlay

WHAT IT DOES

This script scans camera gear product pages and review sites—DPReview, B&H, Adorama, and others—for camera specifications including sensor size, megapixels, ISO range, lens mount, video resolution, burst rate, weight, and dimensions. It displays a floating overlay comparing specs side-by-side for multiple products. Specification data is extracted from the page, organized by product, and displayed in a comparison matrix with color-coded indicators: green for best, red for worst, yellow for average. Key differentiators are highlighted and a summary of relative strengths is provided. Users can export comparison data as CSV or JSON. All comparison snapshots are stored per domain locally for tracking over time.

WHERE IT RUNS

Works on any camera gear product page or review site—DPReview, B&H, Adorama, Imaging Resource, or any page displaying camera specifications. The script detects spec data using common patterns and selectors, making it compatible with most camera gear sites.

HOW TO USE

The panel appears automatically when you visit a product page. It detects products and their specifications, then displays a comparison matrix with products as columns and specifications as rows. Each specification value is color-coded: green for the best value among products, yellow for average, red for the worst. The "Key Differentiators" section shows which specifications vary most between products. Click "Refresh Data" to rescan for updated product information. Export comparison data as CSV for spreadsheet analysis or as JSON for programmatic use. Use "Clear History" to reset stored snapshots for the current domain. The panel automatically saves a snapshot each time you visit, building a history of spec comparisons.

TECHNICAL MECHANISM: CAMERA SPECIFICATION EXTRACTION WITH COLOR-CODED COMPARISON MATRIX

The script uses a comprehensive detection strategy. It searches for product/spec containers using selectors (.product, .specs, .spec-table, .specifications) and falls back to scanning divs and tables with spec-related keywords (megapixel, sensor, resolution, iso, weight, dimension). For each product, it extracts the name from product-name elements or by identifying capitalized text. Specifications are extracted using a defined list of spec definitions with pattern matching: sensorSize, megapixels, isoRange, lensMount, videoResolution, burstRate, weight, dimensions. For each spec, the script checks patterns like "Sensor: [value]" or "Megapixels: [value]" and also scans table rows for label-value pairs. The comparison matrix is built by collecting all spec keys across products and rendering them as table rows. Color coding is applied to numeric values by calculating the relative position of each value within the range: top 30% = green, middle 40% = yellow, bottom 30% = red. Key differentiators are identified by finding specs where products have different values. Each snapshot stores the product list with specs, capped at 30 entries per domain. The export function generates CSV with products as columns and specs as rows.

THE PANEL

The spec comparison overlay appears in a draggable, resizable panel that remembers its position per site. The panel shows the comparison matrix with color-coded specs, key differentiators, and history. Drag by the header to reposition, collapse to a compact icon with a click, and resize using the bottom-right corner. The panel snaps to screen edges for tidy placement and closes with the Escape key. All settings—panel position—persist per website using GM_setValue, so your view returns exactly as you left it.

PLEASE NOTE

This script requires the free BotGentz extension to run. The script relies on common product page structures—if a site uses a non-standard layout, spec detection may be incomplete. The script does not access your retail account credentials—all data is read from the visible page and stored locally. The color coding is based on relative comparison within the detected products; colors indicate best/worst among the current set. The spec extraction uses pattern matching; some specs may be missed if the page uses different labels. All data is stored locally in your browser via GM_setValue and never transmitted.