Docs

Pixel Flow user manual and best practices

Find scanning, filtering, image details, library, export, account, and industry workflow guidance by task.

Core Workflows

Pixel Flow’s core workflow is not just saving one image. It connects page image scanning, filtering, single-image review, favorites, tags, download history, exported records, and backup into one repeatable browser-side process. Use this page to choose the right guide for the task in front of you.

Pixel Flow capture feed showing scanned page images, format filters, size details, and batch action controls
The capture feed is the main entry point. Once the side panel opens, Pixel Flow turns detectable images on the current page into a filterable, selectable, batch-ready list.

Choose Your Task

What you want to doStart hereOutput
Find images from the current pageCapture Page Images in BulkA candidate list of images from the page
Check one image’s source, format, and metadataAnalyze One Image and Its SourceURL, dimensions, format, EXIF, AI/AIGC clues
Keep assets for longer-term projectsFavorite Images and Organize with TagsA tagged local asset library
Save files while preserving contextBatch Download with Source RecordsImage files, download history, and source records
Hand image candidates to a team or clientExport an Image InventoryA reviewable Excel image inventory
Protect data before switching devices or uninstallingMigrate Data and Avoid Data LossA backup package that can be imported later

A Complete Flow

  1. Open the target page, then click the Pixel Flow toolbar icon or choose Manage Current Page Image from the page context menu.
  2. After the side panel opens, the capture feed scans images that are already rendered on the current page. If the page lazy-loads content, keep scrolling so more images enter the viewport.
  3. Use format, aspect ratio, source type, and resolution filters to remove icons, avatars, placeholders, and unrelated small images.
  4. Select candidate images, then use the bottom action bar to preview, favorite, download, or export them.
  5. For images that need review, open image details or the Preview page to check URL, dimensions, format, source page, EXIF, AI fingerprint, and AIGC parameter clues.
  6. For long-term organization, save images to the library and tag them by project, client, purpose, permission status, or delivery stage.
  7. For delivery, download files and keep the download history. For review or collaboration, export an Excel record. Before switching devices, uninstalling, or clearing browser data, create a backup.
Pixel Flow capture feed with selected images and bottom actions for rescan, download history, batch download, batch favorite, quick preview, Excel export, and cancel selection
After selecting images, the capture feed shows actions for rescan, download history, batch download, batch favorite, quick preview, Excel export, and clearing the selection.

How The Interfaces Work Together

Pixel Flow’s interfaces have different jobs. This overview connects them; the linked guides cover detailed button behavior.

InterfaceHandlesOpen it when
Capture feedPage image scanning, filtering, selection, preview, favorites, downloads, and Excel exportYou want to collect images from one page
Image detailsOne image’s basic info, source clues, EXIF, AI fingerprint, AIGC parameters, and download optionsYou need to judge image quality, source, or technical metadata
Preview pageMulti-image preview with left/right navigation and the same detail panelsYou want to compare candidates before downloading or use deep inspect from the context menu
LibraryFavorites, search, filters, tag editing, batch tags, and later downloadsImages have become part of a longer-term project library
Download historyDownload tasks, timestamps, source entry points, and package filesYou need to verify delivered files or trace a previous download
SettingsSign-in, PRO status, scan thresholds, tags, file naming, conversion preferences, backup, and importYou need to change workflow rules or protect local data
Pixel Flow Preview page with a large image on the left and image details, source records, and analysis panels on the right
The Preview page is useful for comparing candidate images and checking source and analysis clues before downloading.

Where To Go Next

If you are new to Pixel Flow, start with First Three-Minute Session to learn the basic motion. After that, choose by task:

  • For the full product map, read Feature Overview.
  • To collect images from a page, open Capture Page Images in Bulk.
  • To check one image’s source and metadata, open Analyze One Image and Its Source.
  • To organize images for ongoing work, open Favorite Images and Organize with Tags.
  • To keep downloads and source context together, open Batch Download with Source Records.
  • To share image records for team, client, or later review, open Export an Image Inventory.
  • Before uninstalling, reinstalling, switching devices, or clearing browser data, open Migrate Data and Avoid Data Loss.
Pixel Flow library showing saved images, tag filters, and an asset list
The library turns temporary images found on pages into searchable, filterable, reusable project material.

Data, Permissions, And Rights Boundaries

Pixel Flow helps preserve source URLs, page context, download history, and exported records, but those records are review clues, not copyright permission. Before publishing, client delivery, commercial use, redistribution, or dataset preparation, separately confirm image rights, site terms, publicity rights, trademark limits, and your internal review rules.

Favorites, tags, download history, settings, and backups primarily depend on browser extension local data. Before uninstalling the extension, clearing browser data, reinstalling Chrome, or moving to a new device, export a backup package from Settings. After import, structured records such as favorites and tags can be restored; some temporary analysis data may need to be regenerated by reopening the image.

Pixel Flow Settings page showing the Data Backup and Migration area with import and backup entry points
Create a backup before switching devices, uninstalling the extension, clearing browser data, or reinstalling, so local asset records and tags are not lost.

Pages