Image reference workflows
How to Review Images in a Grid and a Large Preview
An image grid answers “which candidate is worth another look?” A larger preview answers “what is happening in this candidate?” Using both views prevents a common mistake: approving a picture from a tiny tile or losing the shortlist while inspecting one image. This guide gives a repeatable review pass for a small set of reference images. It is about screening and inspection, not a precise side-by-side pixel comparison or a permanent asset library.
Separate selection from inspection
Before reviewing, write down what you are deciding. For example, a designer may need a landscape with a clear horizon, visible foreground and quiet space for text. The grid lets them compare broad composition across candidates. It is fast because every image is reduced to the same visual scale. That is also its weakness: details can disappear and cropping can change the apparent balance.
A larger preview gives one image room to breathe, but it removes the immediate comparison against the others. Use the two views in sequence. First identify two or three candidates in the grid, then inspect each larger, then return to the grid to make a choice. Do not ask a small tile to establish sharpness or a single preview to rank an entire collection from memory.
Give every candidate a retrievable identity
Save the source page URL and a short label for each candidate before a review session. “Coastal cliff, source page A” is more useful than “image 3.” Keep the original files in a project folder if the site's terms allow download. If you only have search thumbnails, follow the result to the source page first. A board can keep working copies visible, but it cannot replace the records that tell you where an image came from and whether it can be used.
Use the same order in your project note and your working grid. This matters once candidates look similar. If you call an image “the good mountain one” and later rearrange the board, the feedback becomes ambiguous. A simple label, link and one-sentence reason for inclusion is enough. You do not need an elaborate tagging system for a four-image decision.
Make a first pass in the grid
Add only the candidates relevant to the decision to FloatBoard, using the image controls in your installed version. Arrange the app where it does not cover your browser or canvas. The recording above shows a small landscape grid while search results remain nearby. It was captured on Linux in July 2026; treat it as an example of the review pattern, not as a guarantee that every current platform uses identical controls.
Scan the grid for the large signals: horizon position, subject size, overall light and open space. For each image, write one useful observation and one uncertainty. For instance: “Strong silhouette, but foreground may be too dark.” Remove obvious mismatches before opening a larger view. The recorded session eventually includes more images than the current free plan's five images per day; use the current plan limits when planning your own working set.
Open one candidate larger and test the uncertainty
After the grid pass, pick the image whose uncertainty matters most and inspect it larger. Open its source page or original file; if your installed app offers a larger image view, that can be a convenient intermediate look. This is a proposed review step, not an action demonstrated in the clip above. Ask one question at a time: Is the foreground genuinely too dark? Does the subject separate from the background? Is there a usable text-safe area? If the larger view cannot settle a detail, use the source at adequate resolution.
Write the answer next to the candidate label before moving to the next one. This prevents the enlarged image from gaining an unfair advantage simply because it is the most recent image you saw. If the candidate fails, note exactly why: “Important subject clipped in target crop” is actionable; “doesn't feel right” is not. The specific reason also helps you make a better search query later.
Return to the grid before making the final choice
After inspecting the finalists individually, return to the grid and compare them again on the original question. You may find that a picture with beautiful detail in the large preview still loses on composition when seen beside the other candidates. Conversely, a quiet tile may be the strongest background for text. This back-and-forth is the point of having both views, rather than treating the larger preview as a final approval state.
Choose a winner only after a real use test. For a website hero, put the file behind the actual copy at desktop and mobile sizes. For illustration reference, check whether the relevant shape or lighting is visible at your canvas size. For a product image, inspect the source at adequate resolution. The board narrows choices; the actual design context validates them.
Avoid false confidence from scaled images
Neither view proves an image is licensed, high-resolution, color-accurate or suitable for every crop. The grid may use thumbnails, and a larger preview can still be resized or compressed. Return to the original asset for technical checks and the source page for usage terms. If a site offers multiple sizes, confirm the file you plan to use is the one you actually inspected. Do not infer dimensions from how large an app window appears.
If you need exact pixel differences between two photographs, use a tool intended for that comparison or open the originals side by side. Our Windows photo comparison guide covers that use case. A review grid is better at triage: separating promising candidates from weak ones while keeping the broader choice visible.
Turn the visual pass into a decision record
Keep a compact record with four columns: candidate and source, what the grid suggested, what the larger view revealed, and outcome. A sample entry might read: “B: calm sky in grid; larger preview shows busy branches at headline height; reject for hero, keep as editorial image.” This is faster to revisit than a screenshot of the final board and makes the reasoning useful to teammates who were not present.
Once the chosen image is in the project, remove temporary copies from the working board if they are no longer needed. Retain original files and permissions where your team normally stores them. If you are still looking for candidates, the landscape photo shortlist guide explains how to choose a few images with distinct roles before this review pass begins.
Frequently asked questions
Should I judge image quality from the grid?
Use the grid for broad composition and shortlist decisions. Inspect the original file for sharpness, compression and precise detail.
When should I switch to a larger preview?
Switch when a specific uncertainty cannot be settled from the tile. Check one question, record the answer, then return to the grid before deciding.
Do I need to keep every candidate after the review?
Keep the chosen original and its source record. Archive other links only if they may serve a future task; clear temporary working copies that no longer help the current decision.