Skip to main content
Optimize LynxHub’s speed, resource consumption, and graphic rendering capabilities to match your hardware.
Most changes in the Performance settings tab require you to restart the LynxHub application before they take effect.

Rendering and GPU acceleration

Adjust how visual assets and pages are rendered:
  • Use Hardware Acceleration: Enables GPU-assisted UI rendering. If you experience UI freezing, lagging, or black screens, disable this setting to fall back to CPU software rendering.
  • GPU Rasterization: Offloads layout and page drawing tasks to the GPU. This improves scrolling performance and animation smoothness.
  • Zero-Copy GPU Buffers: Optimizes image and video memory transfers directly between your system RAM and GPU VRAM. Disable this if you notice visual glitches or checkerboard rendering artifacts.
  • High DPI Support: Enables high-resolution scaling. This prevents blurry layouts on 4K or high-density monitors.
  • Enable Skia Graphite: Enables Skia Graphite rendering. This uses the Dawn backend by default.

Media and execution

Optimize local script and media execution:
  • Hardware Video Decoding: Uses GPU hardware to decode videos. Disable this if web players freeze or crash during playback.
  • WebAssembly SIMD: Enables Single Instruction Multiple Data (SIMD) vector optimization for WebAssembly runtimes. This improves execution speed for local AI web interfaces.
  • Parallel Downloading: Enables multi-connection downloading to accelerate file download speeds.

JavaScript and cache limits

Manage heap sizes and disk usage:
  • JavaScript Memory Limit: Sets the V8 JavaScript engine’s maximum heap allocation.
    • 2 GB: Minimizes RAM footprint. Good for budget setups.
    • 4 GB (Default): Balanced limit suitable for most developer and user environments.
    • 8 GB: Allocates a larger heap. Useful when loading huge datasets, large AI modules, or complex WebAssembly layouts to prevent “Out of Memory” crashes.
  • Disk Cache Size: Controls how much disk space is allocated to browser caching:
    • Default: Uses browser-managed defaults.
    • 256 MB: Small footprint for devices with limited storage.
    • 512 MB: Balanced cache limit.
    • 1 GB: Large cache capacity to accelerate load times on frequently visited sites.

Display and color

Configure color gamut outputs and autoplay policies:
  • Force Color Profile: Forces the rendering engine to output using a specific color space:
    • Default: System-defined color profile.
    • sRGB: Standard color gamut suitable for most displays.
    • Display P3: Wide color gamut recommended for compatible high-dynamic-range (HDR) screens.
    • Color Spin (Gamma 2.4): Alternative gamma calibration profile.
  • Media Autoplay Policy: Configures when audio and video play automatically:
    • Default: Follows standard browser autoplay restrictions.
    • Allow Autoplay: Allows video/audio to start playing immediately without requiring interaction.
    • Require Gesture: Requires some user interaction (like scrolling or typing) before playing.
    • Require Page Activation: Requires a click or touch event on the page before playback starts.

Advanced hardware overrides

Overrule standard graphics limits for advanced setups:
  • Force High-Performance GPU: Enforces the use of a discrete, high-performance GPU on multi-GPU systems (such as laptops with integrated Intel graphics and a dedicated NVIDIA/AMD graphics card).
  • Ignore GPU Blocklist: Overrides Chromium’s internal driver compatibility checks. This allows you to force hardware acceleration on older or unsupported graphics drivers, but may cause rendering crashes.
  • Disable GPU VSync: Bypasses vertical synchronization limits. This reduces input latency for terminal entries but can cause noticeable screen tearing.
  • Disable Frame Rate Limit: Removes the default 60 FPS rendering cap. Enabling this makes scrolling feel buttery smooth on high-refresh-rate monitors (120Hz, 144Hz+), but increases power consumption and heat generation.
Last modified on July 13, 2026