If wkhtmltoimage produces an image that shows only a thin bar, first check the image’s pixel dimensions. A genuinely short output points toward the capture height or the page’s calculated content height. If the image has full-page dimensions but the visible content is still just a bar, investigate the page’s CSS, viewport-dependent layout, and JavaScript rendering. The symptom alone does not identify a single cause; the URL, command, executable version, output dimensions, and logs are needed to confirm one.
Start by checking the output image dimensions
Open the PNG (or other output image) in an image viewer and inspect its actual width and height in pixels. This separates two different problems that can look similar when you first open the result:
- The image itself is only a few pixels high. Focus first on the height that wkhtmltoimage calculated or was told to use, and on the document’s layout.
- The image has substantial height, but the page content appears only in a strip. The capture area may exist, while CSS clipping, a fixed-height element, an unsuitable viewport, or content that has not rendered is hiding the rest.
The wkhtmltoimage manual says screen height is calculated from page content by default, and documents explicit screen-height and width options. That default makes the output dimensions a useful first diagnostic rather than proof that the page’s full intended content was laid out correctly.
Try a diagnostic capture with an explicit height, adjusting the values and URL for your case:
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →#1 Best Overall
- CRISP CLARITY: This 23.8″ Philips V line monitor delivers crisp Full HD 1920x1080 visuals. Enjoy movies, shows and videos with remarkable detail
- INCREDIBLE CONTRAST: The VA panel produces brighter whites and deeper blacks. You get true-to-life images and more gradients with 16.7 million colors
- THE PERFECT VIEW: The 178/178 degree extra wide viewing angle prevents the shifting of colors when viewed from an offset angle, so you always get consistent colors
- WORK SEAMLESSLY: This sleek monitor is virtually bezel-free on three sides, so the screen looks even bigger for the viewer. This minimalistic design also allows for seamless multi-monitor setups that enhance your workflow and boost productivity
- A BETTER READING EXPERIENCE: For busy office workers, EasyRead mode provides a more paper-like experience for when viewing lengthy documents
wkhtmltoimage --debug-javascript --width 1280 --height 3000 --javascript-delay 1500 'https://example.test/page' page.pngThe 1280-pixel width, 3000-pixel height, and 1500-millisecond delay are examples, not universal settings or tested recommendations. Inspect the output dimensions and content after the run. A larger explicit height may give the renderer a taller capture area, but it will not repair page CSS that clips content or prevent a responsive layout from showing a different version at the chosen width.
Check the page’s layout at the capture width
wkhtmltoimage renders a page in a viewport, so the chosen width can affect which CSS rules apply and how much content fits. Compare the target page in a browser at approximately the same width as the capture. Look for a mobile or narrow-screen breakpoint that collapses the page into a banner, toolbar, or compact application shell.
Look for clipping and fixed-size containers
- Inspect the page and its main content containers for a fixed height that is too small for their contents.
- Check whether
overflow: hiddenor another overflow rule clips content beyond a short container. - Look for elements positioned outside the visible area, including content placed below or beside a constrained wrapper.
- Compare a wider and narrower capture if the layout changes at responsive breakpoints.
A project issue discusses --viewport-size in connection with custom scrollbars or CSS overflow. That is a report about a particular situation, not evidence that changing this option fixes every bar-only capture. Treat viewport changes as a controlled test: keep the page, other settings, and output inspection consistent, then determine whether the layout or clipping changes.
Determine whether the page needs more time to render
Some pages add or expand content after the initial document load. The command-line reference documents --javascript-delay, and the settings reference describes load.jsdelay as a wait after a page has loaded. A short delay can help determine whether timing is involved:
Recommended Free Tools
Rank #2
- CRISP CLARITY: This 22 inch class (21.5″ viewable) Philips V line monitor delivers crisp Full HD 1920x1080 visuals. Enjoy movies, shows and videos with remarkable detail
- 100HZ FAST REFRESH RATE: 100Hz brings your favorite movies and video games to life. Stream, binge, and play effortlessly
- SMOOTH ACTION WITH ADAPTIVE-SYNC: Adaptive-Sync technology ensures fluid action sequences and rapid response time. Every frame will be rendered smoothly with crystal clarity and without stutter
- INCREDIBLE CONTRAST: The VA panel produces brighter whites and deeper blacks. You get true-to-life images and more gradients with 16.7 million colors
- THE PERFECT VIEW: The 178/178 degree extra wide viewing angle prevents the shifting of colors when viewed from an offset angle, so you always get consistent colors
wkhtmltoimage --width 1280 --height 3000 --javascript-delay 1500 'https://example.test/page' page.pngUse a delay as a diagnostic, not as a substitute for knowing when the page is ready. If you control the page, make its rendering readiness deterministic and trigger the capture only after the content you need is present. Increasing the delay indefinitely can make capture slower without fixing an element that never renders or remains clipped.
Do not assume a window-status flag is a universal readiness signal
The project’s issue history records a problem involving --javascript-delay and --window-status in wkhtmltoimage 0.12.2; it was marked fixed in milestone 0.12.2.1. This is historical, version-specific evidence, not a guarantee about every later build. Another reported case involving window-status waiting on a JavaScript-heavy page was closed as invalid. If you use status-based waiting, verify its behavior with your installed executable and page rather than assuming that a status flag reliably means all content is ready.
Check for lazy-loaded or scroll-triggered content
Images, charts, maps, and application content may load only after they enter the visible viewport or after a user scrolls. The wkhtmltoimage project archive includes a report of images loaded only when visible not appearing in a capture. That report does not establish that lazy loading explains every strip-shaped result, but it makes visibility-triggered content worth testing when the missing area contains images or a dynamic application view.
Rank #3
- Clear visuals. Fluid motion: A 144Hz refresh rate and 1ms MPRT deliver smooth, tear‑free motion across work, gaming, and streaming for clearer, more fluid viewing.
- Eye comfort: TÜV Rheinland 3‑star* certification reduces harmful blue light while preserving stunning color quality without compromise. *TÜV Rheinland 3-star eye comfort certification.
- Wide viewing angle: Get consistent views across a wide 178° /178° viewing angle.
- In-Plane Switching (IPS): See excellent color accuracy and consistency across wide viewing angles with In-plane Switching (IPS) technology.
- Ultra-thin bezels: Maximize your viewing experience with thin bezels.
- Open the page in a browser and scroll through the missing area. Note whether images or other content appear only as they approach the viewport.
- Compare the page before and after scrolling, then capture again to see whether the missing content is tied to visibility or page initialization.
- If you control the page, make the required content available before capture, or arrange for its loading to be triggered without relying on a human scroll.
If the page is a map, chart, image strip, or app shell, also check whether the visible bar is simply the initial shell while the rest waits on JavaScript or a visibility event.
Record the version and use JavaScript diagnostics
Before attributing the behavior to a command-line option, record the executable version and check the options supported by that installed binary:
wkhtmltoimage --version
wkhtmltoimage --helpBuilds can differ, and the historical delay issue makes the exact version particularly relevant when investigating JavaScript waits. Do not infer how a local binary behaves only from an option name or from reports about a different release.
Rank #4
- CURVED FOR ENHANCED ENGAGEMENT: An immersive viewing experience with a curved monitor that wraps more closely around your field of vision; It creates a wider view, enhancing depth perception and minimizing peripheral distraction
- SMOOTH PERFORMANCE FOR SEAMLESS CONTENT: Stay in the action when playing games, watching videos, or working on creative projects; The 100Hz refresh rate reduces lag and motion blur so you don't miss a thing in fast-paced moments¹
- MORE GAMING POWER: Gain the edge with optimizable game settings; Color and image contrast can be adjusted to see scenes more vividly and spot enemies hiding in the dark; Game Mode adjusts any game to fill the screen so you can view every detail²
- KEEP IT EASY ON THE EYES: Care for your eyes and stay comfortable, even during long sessions; Advanced eye comfort technology certified by TÜV reduces eye strain by minimizing blue light and reducing irritating screen flicker²
- INCREASED VERSATILITY: Connect to more; Plug devices straight into your monitor for increased flexibility, making your computing environment even more convenient
For a diagnostic run, --debug-javascript can expose JavaScript-related messages. Keep the exact command and logs alongside the output image, then compare the target with a minimal page. Simplifying the test helps distinguish a problem in the target page’s scripts or layout from a more general capture setup issue.
Use a controlled troubleshooting sequence
- Save the evidence. Record the target URL, full command,
wkhtmltoimage --versionoutput, logs, and the image’s pixel dimensions. - Check the dimensions. If the image is unusually short, test an explicit
--heightand inspect the result. If it is tall but shows a bar, prioritize layout and rendering checks. - Hold width constant while testing height. Use a width suited to the page and compare output. This helps avoid confusing a height change with a responsive breakpoint change.
- Inspect CSS and viewport behavior. Check fixed heights, overflow clipping, positioned elements, and breakpoints at the capture width.
- Test rendering time. Use a reasonable
--javascript-delayas a diagnostic and review--debug-javascriptoutput. If you own the page, prefer an explicit readiness condition. - Test visibility-dependent content. Check whether scrolling or entering the viewport causes the missing content to load.
- Change one variable at a time. Compare dimensions and visible content after each change. Avoid treating a successful-looking run as proof of a general fix unless the same conditions reproduce it.
Common symptoms and what to try
| What you observe | What it suggests | Next check |
|---|---|---|
| The output file is only a few pixels high | Capture height or calculated document height may be too small. | Try an explicit --height; inspect the page’s content layout and dimensions. |
| The image is tall, but the content is a strip | The capture area may be tall while CSS clips content or layout differs at the viewport width. | Check fixed-height wrappers, overflow, positioned elements, and responsive breakpoints. |
| Content appears after waiting | Rendering may continue after initial load. | Use a delay to diagnose timing; where possible, make page readiness explicit. |
| Images or sections appear only after scrolling | Content may depend on lazy loading or viewport visibility. | Test the page’s visibility behavior and arrange for needed content to load before capture. |
| A delay or status option behaves unexpectedly | Version-specific behavior or a page-specific readiness condition may be involved. | Record the binary version, inspect its help output, and test the exact page and command. |
Or skip the browser setup
If you need a screenshot without diagnosing a local wkhtmltoimage rendering setup, ScreenshotNeo is a website screenshot API and MCP server. One GET request can return a PNG, JPEG, WebP, or PDF. For a WebP screenshot of Stripe, the cURL request is:
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorscurl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for request options and setup. ScreenshotNeo accepts cookie or consent banners as a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each of those steps can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and each response reports the page verdict and billing status in headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents using Claude, Cursor, or another MCP client. The Free plan includes 1,000 screenshots per month without a card; paid plans start at $5 for 3,000 screenshots.
Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month with no card.
Best Value
- 【INTEGRATED SPEAKERS】Whether you're at work or in the midst of an intense gaming session, our built-in speakers provide rich and seamless audio, all while keeping your desk clutter-free.
- 【EASY ON THE EYES】 Protect your eyes and enhance your comfort with Blue-Light Shift technology. This feature reduces harmful blue light emissions from your screen, helping to alleviate eye strain during long hours of use and promoting healthier viewing habits.
- 【WIDEN YOUR PERSPECTIVE】Our sleek minimal bezel design ensures undivided attention. The nearly bezel-free display seamlessly connects in a dual monitor arrangement, delivering an unobstructed view that lets you focus on more at once, completely distraction-free.
What information confirms the cause?
A bar-only image is a symptom, not a diagnosis. To narrow it to a specific cause, keep the exact page URL, installed wkhtmltoimage version, full command line, output pixel dimensions, and JavaScript logs together. Compare those details with the page’s layout at the capture width and with whether its content depends on rendering time or scrolling. The available reports and documentation support these checks, but do not establish one universal cause or fix.
Frequently Asked Questions
Does a bar-shaped screenshot mean wkhtmltoimage is broken?
Not by itself. The symptom can result from a short output dimension, clipped or viewport-dependent page layout, or content that has not rendered; the exact command and output are needed to distinguish them.
Is 3000 pixels the correct height for every full-page capture?
No. It is only an example diagnostic value. Choose a height appropriate to the page and verify the resulting image dimensions and content.
Will adding a JavaScript delay always make a dynamic page render correctly?
No. A delay is useful for testing whether timing matters, but it cannot guarantee that content will load or that a page-specific readiness condition has been met.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
