The developers behind Blender are weighing whether to retire OpenGL support from the open-source 3D suite, with a report from Phoronix describing maintainer-level discussion about dropping the long-standing graphics API in Blender 6.0.
The trigger, according to that report, is the maturation of Blender's Vulkan path. Vulkan support in recent Blender releases has grown steadily — to the point where the project now describes it as mature — weakening the case for maintaining two separate rendering backends.
The important qualifier is that this remains a direction of travel, not a decision with a timeline attached. The Phoronix coverage points to developer conversation rather than an announced plan: no version has been committed to, no deprecation window has been published, and no roadmap entry has been issued. If maintainers do commit to removing OpenGL, the current release line would likely be the last one carrying it for an extended period — but that inference is speculative at this stage, and readers should treat any version-specific claim circulating outside the source as premature.
The project's own history argues for patience. OpenGL has been Blender's rendering backbone for the better part of two decades, and every previous graphics-stack transition in the software has involved extended periods where both paths remained available. Vulkan, meanwhile, only recently reached the point where its performance and feature parity justify the discussion at all.
Where the question becomes concrete is on the operational edges of the rendering stack. Headless rendering nodes, CI workers, and farm workers are often configured against whichever backend has historically been cheapest to provision — which, for many installations, still means OpenGL on older GPU drivers. Remote display sessions and virtualised GPU pass-through setups are another area where driver behaviour differs sharply between the two APIs. Studios that refresh hardware on a three-to-five-year cycle are the ones who will feel this most: a machine that still renders reliably under OpenGL may not have a current enough driver stack to run Vulkan cleanly, and the gap between "supported" and "actually works in production" is where upgrade projects quietly stall.
On Linux, the driver ecosystem adds another wrinkle. Mesa's Vulkan drivers for Intel, AMD, and increasingly NVIDIA hardware have come a long way, but coverage still varies by card generation, and older discrete GPUs in workstation towers remain in service well past their vendor's support horizon. For those users, an OpenGL removal would not be an abstract API change — it would be the point at which Blender effectively requires new hardware.
For now, the sensible posture is monitoring rather than migration. Nothing about the current discussion forces anyone to abandon OpenGL workflows, and the project has not indicated when — or whether — the change will be made. Organisations planning workstation refreshes over the next couple of years may want to factor Vulkan readiness into GPU procurement decisions, but there is no evidence today that urgent action is warranted.
There is also an ecosystem angle worth flagging. Khronos Group keeps OpenGL in maintenance rather than development mode, and other digital content creation tools have already begun leaning on Vulkan or newer low-overhead graphics APIs. Seen against that backdrop, Blender's discussion looks less like an isolated rumour and more like part of a wider trend — though the comparison is suggestive rather than conclusive, and the source itself stops well short of declaring an industry shift.
What the source does establish is narrower, and clearer: a project as conservative as Blender is having this conversation in public, without a roadmap attached. That is the news. When — or whether — the conversation becomes a deprecation plan is an open question, and anyone claiming otherwise is reading ahead of the evidence.
Source: Phoronix, "Blender 6.0 May End Up Removing OpenGL Support."
Blender 的開發團隊正在權衡是否從這套開源 3D 軟件中淘汰 OpenGL 支援，一份來自 Phoronix 的報道描述了維護者層面就於 Blender 6.0 移除這項沿用已久的 graphics API 所展開的討論。
據該報道所述，觸發因素是 Blender Vulkan 路徑日趨成熟。Vulkan 支援在近期 Blender 版本中穩步進步——已達到該項目現時稱之為「成熟」的水平——令同時維護兩套獨立渲染後端（rendering backend）的理據進一步減弱。
必須留意的關鍵限定是：這仍然只是一個發展方向，並非已附有時間表的決定。Phoronix 的報道反映的是開發者之間的對話，而非正式公布的計劃——目前尚未鎖定任何版本號、未發布棄用緩衝期，亦未在 roadmap 上新增條目。若維護者最終確實決定移除 OpenGL，現行版本系列很可能將是最後一個在較長時間內仍保留該 API 的系列——不過此推測現階段仍屬揣測，讀者不應將流傳於原始出處以外的任何具體版本說法當作事實。
該項目的歷史本身表明應保持耐心。OpenGL 作為 Blender 的渲染核心已有近二十年之久，過去每一次 graphics stack 過渡都經歷了兩條路徑並行可用的長時間階段。與此同時，Vulkan 直至最近才達致其性能與功能足以令今次討論成立的水平。
真正使問題變得具體的，是渲染 stack 的操作層面。Headless 渲染節點、CI worker 以及 farm worker 往往按照歷來配置成本最低的後端設置——對許多安裝而言，這仍代表在較舊 GPU 驅動程式下運行 OpenGL。遠端 display session 及 virtualised GPU pass-through 環境，則是兩種 API 之間驅動程式行為差異最為顯著的另一領域。以三至五年週期更新硬件的工作室最受影響：一台在 OpenGL 下仍可靠渲染的機器，其驅動程式 stack 可能不足以順利運行 Vulkan，而「受支援」與「在實際生產環境中可用」之間的落差，正是升級項目悄悄停滯的地方。
在 Linux 上，驅動程式生態又增添一重變數。Mesa 為 Intel、AMD 及日漸包括 NVIDIA 硬件而設的 Vulkan 驅動程式雖已長足進步，但覆蓋度仍因顯卡代數而異，工作站機箱內的舊型獨立 GPU 在廠商支援期結束後往往仍在服役。對這些用戶而言，移除 OpenGL 並非抽象的 API 變更——那將是 Blender 實質上要求全新硬件的時刻。
現階段，合理的姿態應是持續觀察而非即時遷移。目前的討論並未迫使任何人放棄 OpenGL 工作流程，項目方面亦未表明該變更會於何時——或是否會——作出。計劃於未來數年更新工作站的機構，或應在 GPU 採購決策中納入 Vulkan 準備度的考量，但目前沒有證據顯示有必要採取緊急行動。
另有一個值得指出的生態層面。Khronos Group 將 OpenGL 置於維護而非開發模式，其他 digital content creation 工具亦已開始轉向 Vulkan 或更先進的低開銷 graphics API。在這一背景下觀察，Blender 的討論與其說是一則孤立傳聞，不如說是更廣泛趨勢的一環——惟此對比屬提示性而非結論性，原始出處本身亦遠未斷言行業轉向已然成立。
原始出處所確立的範圍較窄，卻更清晰：像 Blender 這樣向來保守的項目，如今正就此事公開討論，且尚無 roadmap 相連——這才是新聞本身。討論會否——以及何時——演變成正式的棄用計劃，仍是懸而未決的問題，任何聲稱已有定論者，都是在超前於證據作出判斷。
資料來源：Phoronix，〈Blender 6.0 May End Up Removing OpenGL Support〉。