How to Make Website Thumbnails for a Behance Portfolio Roundup

Behance calls a project thumbnail its cover image: a preview of the work inside the project. For a website portfolio roundup, prepare a recognizable image for each project, upload it at least 808 × 632 px, and check the crop at Behance’s displayed cover size of 202 × 158 px. Behance lets you choose an image already in the project or add a separate cover image, then adjust its crop. Behance’s cover image guide explains the purpose and crop workflow.

1. Decide what each cover should communicate

A cover is a tiny preview, so choose one clear idea for each roundup entry: the website’s visual identity, a distinctive interface detail, or the theme of the collection. A strong homepage hero, product screen, or unusual navigation detail can work if it remains recognizable when reduced.

For a roundup-wide cover, use one representative image or a deliberately simple composition. A collage of many tiny browser screenshots may make every site hard to identify. Behance does not prescribe a design treatment here; this is practical composition guidance based on the cover’s preview role and compact display size.

2. Capture or prepare the website image

You can use an existing project image or add a separate image just for the cover. For a website roundup, a browser screenshot gives you a direct record of the site’s appearance. Capture the most informative area, and decide whether the cover should show the full page or a focused section.

Capture with a browser you control

For a one-off image, open the site in a browser, set a useful window size, dismiss or close overlays if appropriate, and capture the page. For repeatable captures, automate a browser using Playwright. This example saves a full-page PNG and is runnable with Node.js:

npm install playwright
npx playwright install chromium

// screenshot.mjs
import { chromium } from 'playwright';

const url = process.argv[2] ?? 'https://example.com';
const browser = await chromium.launch({ headless: true });
const page = await browser.newPage({
  viewport: { width: 1440, height: 1000 },
  deviceScaleFactor: 1
});

try {
  await page.goto(url, { waitUntil: 'networkidle', timeout: 60000 });
  await page.screenshot({ path: 'website.png', fullPage: true });
} finally {
  await browser.close();
}

Run it with node screenshot.mjs https://example.com. Replace the example URL with a site you are permitted to capture. Some sites keep network connections open or load content on scroll; if networkidle never occurs, use waitUntil: 'domcontentloaded' and wait for a specific selector or a short, deliberate delay instead. A full-page capture can also be extremely tall, so a focused viewport screenshot may be a better cover source.

Prepare the image for the cover

Keep the subject large enough to read at card size. Crop out browser chrome unless it is part of the visual story.
Make a landscape source at least 808 × 632 px. That is Behance’s stated minimum for a cover image; a larger source gives the crop room.
Use RGB when color fidelity matters. Behance accepts CMYK but converts it for display, which can alter colors.
Export as JPEG or PNG. Behance recommends images no wider than 2800 px and under 10 MB for general image use. It does not accept images over 50 MB.
Preview a 202 × 158 crop. Check that the site identity or focal detail survives the reduction, and move the crop if needed.

The cover-specific minimum and general image guidance serve different purposes. Behance’s general guide says project images display at 1400 px wide in Project View and up to 2800 px in Lightbox View; images under 1400 px appear at their uploaded size with side padding in Project View. Those project-content display details do not change the cover’s 202 × 158 px display size. See Behance’s image formatting guide.

3. Set the Behance cover and publish

Add the website image to the project, or have a separate cover image ready.
Open the project details and choose Edit Cover Image.
Select an image already in the project or add another image.
Adjust the crop so the important site detail stays inside the visible frame, then continue.
Review the cover at its compact 202 × 158 px proportion, along with the project title and other details.
Before publishing, ensure the project has a cover image, a title, and at least one creative field. These are required project fields according to Behance’s publishing guide.

4. Keep a roundup visually consistent

For a set of entries, use a consistent crop approach, spacing, and title treatment so the cards feel related. Preserve a distinct identifying detail for each website so consistency does not make the sites look interchangeable. These are editorial recommendations, not Behance requirements or a promise of better engagement.

Behance’s best-practices guidance recommends a focused selection of strong work and says project and image tags affect internal search and search-engine performance. Relevant tags and a clear project presentation are useful context, but they do not guarantee ranking or traffic. See Behance’s best-practices guide.

5. Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. One GET request returns an image or PDF, and its API accepts common screenshot API parameter names. The following cURL example saves a WebP capture; replace the URL and provide your API key. See the ScreenshotNeo API documentation for options including full-page capture, element selection, viewport and device presets, retina scale, custom CSS, waits, and image formats.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

For a roundup, cookie banners are accepted like a visitor and 60+ known consent platforms, newsletter popups, and chat widgets are removed before capture; each step can be turned off. Bot checks, blank pages, timeouts, and failed loads are not billed, and cache hits cost nothing. Responses include X-Page-Verdict and X-Billed headers. An MCP server gives AI agents tools to take screenshots, get page information, and capture PDFs. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Sign up for ScreenshotNeo’s free plan.

Troubleshooting

Problem	Likely cause	What to do
The cover looks blurry	The source is below Behance’s 808 × 632 px cover minimum, or the important content occupies too little of the crop.	Export a larger source, then recrop around the key visual. Inspect at the small cover proportion.
The subject is cut off	The source aspect ratio differs from the cover frame or the focal element is too close to an edge.	Adjust the cover crop in Behance. Leave visual breathing room around the focal point in the source.
Colors changed after upload	The source may be CMYK; Behance converts CMYK for display.	Convert to RGB before export when color accuracy matters.
Upload is rejected	The file may exceed the 50 MB maximum, use an unsupported format, or be missing required project details.	Use JPEG or PNG, reduce the file size, and confirm the project has a cover, title, and at least one creative field. PDF uploads are not supported as project images.
Automated capture hangs	The site may keep network activity open or load indefinitely.	Try `domcontentloaded`, wait for a specific element, and set a timeout. Avoid treating network idle as a universal readiness signal.
Screenshot misses lazy-loaded content	The page loads images only as they approach the viewport.	Scroll through the page before capture or capture a specific viewport region. For an automated workflow, wait for the relevant image or selector before saving.

Performance, reliability, and cost notes

Keep source files manageable. Behance recommends general images under 10 MB and no wider than 2800 px; large files can take longer to prepare and upload. Its hard maximum is 50 MB.
Use a repeatable capture setup. Set viewport size, device scale, wait condition, and target consistently if producing many roundup images. Site content can vary by time, location, cookies, and responsive layout.
Check access and licensing. A publicly visible page is not automatically free to reproduce. Follow the site owner’s terms and obtain permission where needed.
Account for API usage. With ScreenshotNeo, only clean shots are billed; failed captures and cache hits cost nothing. Plans are Free (1,000/month), Starter ($5 for 3,000), Growth ($15 for 15,000), Pro ($39 for 60,000), Scale ($99 for 250,000), and Business ($249 for 1,000,000). Yearly billing gives two months free; every feature is on every plan.

FAQ

Can I use a website screenshot as a Behance cover?

Yes, if it is an image of the work represented in the project and you have the rights to use it. Behance allows selecting a project image or adding a separate cover image.

Can the same image be both a project image and the cover?

Yes. The cover workflow lets you choose an image already included in the project, or add a separate one.

Does Behance use the middle frame of an uploaded video as a project cover?

Behance says an uploaded video uses its middle frame automatically. For a Vimeo embed, a creator can choose a poster image. Video thumbnail behavior is separate from setting a project cover image. See Behance’s audio and video guide.

Should I upload a PDF as the cover?

No. Behance does not support PDF uploads as project images; convert the page you need to JPEG or PNG.