What this changes
PDF pages can be visually complex. Redrawing an entire page for every text move, style change, selection update or layer change wastes work, can flicker and can hide unsafe cleanup decisions.
ArchitectureBrowser-native document runtime architectureA public architecture view of Browser Core: browser-side preview, PDFium-backed rendering, deterministic operations and backend-authoritative export.RuntimeA browser-side runtime for safe realtime document interactionHow Browser Core coordinates browser-local preview, runtime readiness, replayable operations, safe compositing and backend-authoritative export.Render graphRender graph planning for safe browser PDF previewHow Browser Core turns local document edits into structured visual responsibilities, command buffers, tile resolution and safe final preview output.PDFium WASMPDFium WASM for accurate browser-side PDF previewHow Browser Core uses PDFium WebAssembly for local page rastering, text awareness, textless tiles and safer live PDF previews.Textless tilesTextless tiles for cleaner PDF text editing previewsHow Browser Core removes old PDF text from live preview with small PDF-aware clean tiles instead of fake white overlay masks.Local-firstLocal-first PDF preview with backend authorityHow Browser Core gives PDF editing immediate browser-side preview while keeping save, export and persisted document state backend-authoritative.Operation replayOperation replay for refresh-safe document previewsHow Browser Core keeps local edits visible across refreshes while preserving backend-authoritative save and export.Dirty renderingDirty rendering for focused, safe PDF preview updatesHow Browser Core tracks what changed in the live preview using dirty nodes, dirty regions, command buffers and safe final compositing.Debug visibilityDebug visibility for browser-side PDF runtimesHow Browser Core makes local PDF preview behavior observable across operations, render graph state, dirty rendering, tiles, interaction and performance.Technology previewTechnology preview status for Browser CoreCurrent Browser Core technology preview status: browser runtime active, PDFium-backed preview path, backend-authoritative export and roadmap limits.RoadmapBrowser Core engineering roadmapThe Browser Core roadmap for stable local PDF editing, safer visual cleanup, broader document coverage and production-grade save/export workflows.SDK directionFuture SDK direction for embedded document runtimesFuture SDK direction for embedding Browser Core style document runtime capabilities into document products.ArticleWhy PDF editors feel slowBackend render loops make every edit wait for network and regeneration. A browser runtime can make preview feel immediate.ArticlePDFium WASM browser renderingWhere PDFium WebAssembly fits in a browser-side preview path for page raster work, text readiness and clean composition.ArticleTextless tile renderingWhy source-suppressed tiles are cleaner than white overlay masks for PDF text replacement previews.ArticleLocal-first document runtimeHow browser-owned preview sessions and backend-authoritative export can work together without pretending the browser is the final source of truth.ArticleRender graph document editingA public render graph story for document preview, affected regions and predictable compositing.ArticleDirty region rendering in the browserWhy affected-region rendering matters when small edits should not redraw the entire document preview.ArticleOperation replay for document editingRecovering local preview state with deterministic operations while clearing committed work after backend save.ArticleBrowser runtime vs backend render loopA practical comparison of local interactive preview and backend-authoritative PDF save/export.ArticleDebug visibility for document enginesWhy document runtimes need visible health, replay status, provider state and frame timing without exposing private internals.ArticleGPU document rendering roadmapHow GPU compositing can evolve browser-native document runtimes after the safe Canvas/PDFium-backed path is established.
No results found.
Dirty rendering for focused, safe PDF preview updates
Dirty Rendering tracks what changed in the live preview so Browser Core can update the relevant visual work without treating every edit as a full-page redraw.
Technology previewPDFium WASM activeReplay enabled
Runtime pipeline
From PDF bytes to final composite, all inside the browser preview path.
01User operation
02Dirty nodes
03Dirty regions
04Command buffer
05Safe composite
Local-firstDeterministicReal-time previewBackend-authoritative export
Browser Core approach
Runtime-first preview
Browser Core separates dirty nodes from dirty regions. Dirty nodes describe what visual responsibility changed, while dirty regions describe where it changed. The runtime then updates command buffers and only promotes safe work into the final composite.
What this solves
Focuses rendering work on the affected source and replacement areas
Avoids turning small text moves into broad cleanup rectangles
Keeps the previous safe frame visible while required cleanup tiles are pending
Makes performance issues easier to separate from tile rendering or interaction timing
Current status
Semantic dirty nodes
Bounded dirty regions
Inspectable dirty commands
Safe-frame continuity
Frame and composite metrics
Continue learning
Technology preview