Visual Basic 6 shipped in 1998, and Microsoft retired mainstream support for it decades ago — yet developer Wiesław Šoltés just built the entire classic IDE from scratch to run in a browser tab. No virtual machine. No installation. Just HTML, CSS, and JavaScript. The project, called VB6 Studio Web, is live on GitHub and it recreates the full rapid application development loop that made VB6 famous: drag a button onto a form, double-click it, write some VB-style code, press Run.
TL;DR: VB6 Studio Web is a browser-native classic Visual Basic IDE built entirely in HTML, CSS, and JavaScript by developer Wiesław Šoltés. It ships a form designer, a VB-style source runtime, a browser control library, a debugger, WebGPU-based drawing, and a single-file HTML application exporter. According to the author, it delivers the full RAD loop — build any app, then export it — without installing anything.
What Exactly Is VB6 Studio Web?
VB6 Studio Web is a complete recreation of the classic Visual Basic development environment that runs natively in the browser. The GitHub repository describes it precisely: “a browser-native classic Visual Basic IDE, form designer, source runtime and controls library in HTML, CSS and JavaScript, with a debugger, WebGPU drawing and single-file HTML app export.” Every component listed there is part of a single self-contained package.
That packaging matters. Because the whole thing lives in web technologies, there is nothing to download, nothing to configure, and nothing to keep updated. The IDE, the runtime, and the compiler pipeline all execute client-side.
The feature list from the repository reads like a checklist of what made the original VB6 experience distinct:
- A visual form designer for laying out user interfaces
- A VB-style source runtime that executes classic Basic code
- A browser control library covering the standard widget set
- An integrated debugger with breakpoints and stepping
- WebGPU-based drawing for rendering
- A single-file HTML application exporter
- A classic IDE shell that mirrors the original tool window layout
Šoltés summarized the ambition in one line on X: “Imagine you can build any app in RAD.” The claim is bold, but the architecture backs it up — this is not an emulator running a copied binary, it is a reimplementation from the ground up.
Who Built It and Why Does It Matter?
The author is Wiesław Šoltés (@wieslawsoltes), a developer known in open-source circles for building ambitious tooling projects. He announced VB6 Studio Web on X with a compact description covering the IDE, the VB-style source runtime, the form designer, the browser control library, the debugger, and the single-file HTML exporter. The code is published on GitHub under his account, with a mirror repository under the devOp1 account carrying the same description.
Why does this matter? Because Visual Basic 6 occupies a strange place in software history. Millions of business applications were written with it, and coverage of the project — including pieces on DEV Community and GeekNews — frames it as the classic IDE reviving inside the browser. The GeekNews summary highlights the form designer tools and a sample Northwind Traders order-entry application shipped as a demo.
There is prior art, and sources are careful to draw the line. The QWE AI Academy guide notes that “WebVB Studio is a polished free IDE with VB6-style syntax plus Python. Useful. Different job.” In other words, other tools offer VB-flavored syntax. What “just dropped,” according to that same guide, is “the classic shell feel plus a runtime, dozens of controls, a real debugger loop” — the complete loop rather than a lookalike. This project also continues a thread Šoltés explored earlier: devclass reported in November 2024 that he had recreated Visual Basic 6 as a cross-platform IDE in modern .NET, described as being “just ‘for fun.‘” The browser version is the next step of that obsession.
How Does the Form Designer Work?
The form designer is the heart of the RAD experience, and VB6 Studio Web rebuilds it faithfully. You get the classic interaction model: select a control from a toolbox, drop it onto a form surface, drag it into position, and set its properties in a Properties panel. The screenshot of the demo application shows exactly this workflow — a Properties panel displaying a cmdClose CommandButton with Height 495, Width 1305, Top 5820, and Left 8115. Those are recognizable VB6-style coordinate values, down to the twips-like granularity of the original layout system.
The demo project itself proves the designer is not a static mockup. It renders a Northwind Traders order-entry form — frmOrders — with customer information fields, an order items list, an “Add an Item” section with product and quantity inputs, and buttons for New order, Save order, and Close. The Project Explorer shows the familiar structure: Project1.vbp containing forms frmOrders.frm and Form1.frm plus a module modUtilities.bas. That file layout mirrors real VB6 projects.
What does this mean in practice? A developer who used VB6 twenty-five years ago can open this IDE and be productive immediately. The window title bar even reads “Project1 - Microsoft Visual Basic [design]” — a deliberate echo of the original design-time mode. Sources describing the project emphasize that the designer is paired with the control library and runtime, so what you lay out visually is what the runtime executes.
What Does the VB-Style Source Runtime Do?
A form designer alone would be a toy. The runtime is what turns layouts into applications. VB6 Studio Web includes a “VB-style source runtime” — a code execution engine, written in JavaScript, that interprets Basic-style source written against the forms and controls in your project.
Here is the loop the repository and the author’s announcement describe. You design a form. You write event-handling code in a VB-style dialect. You press Run. The runtime binds your source to the live form, wires up control events, and executes your logic inside the browser tab. No compilation step to a separate artifact is required for development — the source runs directly.
The demo application again shows what this looks like end to end. The Northwind Traders order-entry form computes an order total of $107.00 from four line items (Chai x2 at $36.00, Chang x1 at $19.00, Aniseed Syrup x3 at $30.00, Chef Anton’s Seasoning x1 at $22.00). That arithmetic, the item add/remove behavior, and the status bar counting “4 items in order” all flow through the runtime executing project code against the designed form.
The export story completes the picture. The single-file HTML application exporter takes a finished project and produces one standalone HTML file containing the app. The QWE AI Academy guide’s framing is blunt: the differentiator is “the classic shell feel plus a runtime, dozens of controls, a real debugger loop, and” — the export being the visible payoff. Build in the IDE, run via the runtime, ship as one file.
How Real Is the Debugger?
Debugging is where most IDE recreations fall apart, and it is precisely where VB6 Studio Web makes its strongest claim. The GitHub description lists “a debugger” as a first-class component, on equal footing with the designer and runtime — not a bonus feature bolted on later.
What does “real” mean here? The QWE AI Academy hands-on guide is explicit, calling it “a real debugger loop.” That phrasing matters. A debugging loop means the cycle developers actually rely on: pause execution at a breakpoint, inspect state, step through lines, resume, repeat. The runtime supports interruption and stepping rather than merely printing errors to a console.
| Component | Role in the debugging workflow |
|---|---|
| VB-style source runtime | Executes project code and supports pausing |
| Debugger | Breakpoints, inspection, and stepping through the loop |
| IDE shell | Classic design/run/debug mode switching |
| WebGPU drawing | Renders forms and controls while execution is live |
Notice how the pieces interlock. The debugger cannot exist without the source runtime, because it must intercept interpretation mid-flight. The IDE shell’s mode model — the ”[design]” state visible in the demo’s title bar — echoes VB6’s design-time versus run-time distinction, which the debugger extends into break-time.
Is it identical to the Visual Basic 6 debugger from 1998? The sources do not claim feature parity line by line. What they do claim, consistently, is that the loop is real: set a breakpoint in your Basic-style source, hit it while the form is live, step, inspect. For a project built in HTML and JavaScript, that alone separates it from syntax-only VB revivals.
Frequently Asked Questions
Do I need to install anything to run VB6 Studio Web?
No. The project is browser-native, built entirely in HTML, CSS, and JavaScript, and hosted as a web application. The author’s announcement stresses that you can build and export applications “without installing anything,” and the code on GitHub confirms there is no native runtime component.
Is this an emulator running the original Visual Basic 6?
No. VB6 Studio Web is a reimplementation — the GitHub repository describes a form designer, source runtime, and controls library “in HTML, CSS and JavaScript.” The QWE AI Academy guide distinguishes it from tools like WebVB Studio, which offer “VB6-style syntax plus Python” but, as the guide puts it, a “different job.”
What can I do with the single-file HTML export?
You can take an application built in the IDE and export it as one standalone HTML file that runs on its own. The author framed the broader vision on X: “Imagine you can build any app in RAD.” The exported file bundles the app for distribution outside the IDE.
Who is behind the project?
Wiesław Šoltés, who publishes code on GitHub under @wieslawsoltes. He previously recreated Visual Basic 6 as a cross-platform IDE in modern .NET — devclass described that 2024 effort as done “just ‘for fun’” — and the new browser version extends that work.
Summary
VB6 Studio Web proves that a beloved twenty-five-year-old development environment can be rebuilt, faithfully, with nothing but web standards. Here are the key points:
- Developer Wiesław Šoltés built a complete classic VB6-style IDE in HTML, CSS, and JavaScript, published on GitHub
- It includes a form designer, VB-style source runtime, browser control library, debugger, WebGPU drawing, and single-file HTML export
- The demo Northwind Traders order-entry application shows the full loop working: designed form, live runtime logic, computed totals
- Commentators highlight the “real debugger loop” and “classic shell feel” as what separates it from earlier VB-syntax-only revivals
- No installation is required — everything runs client-side in the browser
Curious? Open the GitHub repository, load the demo project, and drag a button onto a form. The RAD loop is waiting.
What Is the Browser Control Library?
A browser control library is the component of VB6 Studio Web that recreates classic Visual Basic controls as native HTML, CSS, and JavaScript elements, so forms designed in the IDE behave like real VB6 forms inside a browser tab. The project’s GitHub repository describes it as one of the core building blocks, sitting alongside the form designer, the VB-style source runtime, and the debugger. In other words, when a developer drops a CommandButton or a Label onto a form, the library supplies the browser-native equivalent that renders and responds to events.
This matters because a RAD environment is only as good as its controls. Classic VB6 development revolved around a toolbox of familiar widgets — buttons, text boxes, labels, and more — and the QWE AI Academy hands-on guide notes that this recreation includes “dozens of controls” plus a real debugger loop. That combination is what separates a visual novelty from a usable tool.
The library also underpins the exported applications. Since the export produces a single-file HTML app, the controls must be self-contained within that file — no plugin, no separate download, no runtime to install. The GeekNews coverage highlights the form design tools and a Northwind Traders order entry example, which demonstrates the controls library working together in a realistic business form scenario.
Why does this approach matter for old-school developers? It means the mental model of VB6 — drag a control, set a property, write an event handler, press Run — translates directly to a medium anyone can open.
How Does Single-File HTML App Export Change RAD?
Single-file HTML application export is the feature that turns VB6 Studio Web from an IDE curiosity into a deployment story: the finished form designs, VB-style code, and control library are packaged into one standalone HTML file. Wiesław Šoltés’ announcement explicitly lists a “single-file HTML application exporter” among the toolchain’s components, alongside the IDE, runtime, form designer, and debugger.
The classic RAD promise was always “build any app fast.” Šoltés frames it exactly that way: “Imagine you can build any app in RAD.” But classic VB6 deployment involved compiled executables and runtime dependencies. Here, the deployable artifact is a single HTML file.
That changes the practical workflow in several ways:
- Design a form in the browser-native form designer.
- Write and debug VB-style source code within the same environment.
- Export the finished project as one self-contained HTML file.
- Share or run the exported app anywhere a browser exists.
- Skip installers, dependencies, and platform-specific builds entirely.
- Keep the full debugger loop during development, per the project’s GitHub description.
- Rely on WebGPU drawing for rendering inside the exported result.
- Treat the browser itself as the universal runtime.
The result is a distribution model that classic VB6 never had. A completed application lives in a file you can email, host statically, or open locally. The QWE AI Academy guide emphasizes that this project combines the classic shell feel with a runtime, dozens of controls, and a real debugger loop — and export closes that loop into an artifact. For developers who remember RAD as the fastest path from idea to working software, this restores the promise with a modern, dependency-free delivery format.
What Role Does WebGPU Play in the Project?
WebGPU is the modern graphics API that VB6 Studio Web uses for drawing, according to the project’s GitHub repository, which lists “WebGPU drawing” as one of its headline features. In a browser-native recreation of a visual IDE, rendering quality and speed matter enormously — every form, control, and design-time surface has to be drawn on screen.
Why WebGPU instead of older canvas-based approaches? The repository positions WebGPU drawing as part of the core technology stack, meaning the IDE’s visual output relies on the browser’s modern GPU-accelerated pathway rather than software-only rendering. For an environment that includes a form designer, a controls library, and a debugger — all rendering simultaneously — that choice supports responsive interaction inside a single browser tab.
The visual evidence from coverage reinforces how complete the rendering is. Screenshots show a faithful classic IDE layout: a design-mode window titled like the original Microsoft Visual Basic shell, a Properties panel displaying exact control geometry (a cmdClose CommandButton with Height 495, Width 1305, Top 5820, Left 8115), and a Project Explorer listing forms such as frmOrders.frm, Form1.frm, and a modUtilities.bas module. Reproducing that pixel-level IDE chrome is exactly the kind of drawing workload WebGPU is suited for.
There is also a forward-looking aspect. Because WebGPU is a standard browser technology, the drawing layer requires no plugins or extensions. The exported single-file HTML apps inherit the same rendering approach, so a finished application draws identically wherever it runs. In short, WebGPU is the engine behind the project’s claim to be genuinely browser-native rather than a styling exercise.
How Does It Compare to Other VB6 Revival Efforts?
VB6 Studio Web is not the first attempt to bring Visual Basic 6 back to life, but sources show it takes a distinctly different route than earlier projects. The most direct comparison comes from devclass.com, which published a piece in November 2024 titled “Visual Basic 6 recreated as a cross-platform IDE in modern .NET – just ‘for fun’.” That effort focused on desktop tooling, rebuilding the IDE experience in .NET for cross-platform desktop use.
VB6 Studio Web, by contrast, targets the browser directly. The QWE AI Academy guide draws another useful line, distinguishing this project from WebVB Studio — described as “a polished free IDE with VB6-style syntax plus Python” — noting that the newer effort offers “the classic shell feel plus a runtime, dozens of controls, a real debugger loop,” and more.
Here’s how the landscape looks based on available coverage:
| Project | Platform | Approach |
|---|---|---|
| VB6 Studio Web (wieslawsoltes/VB6) | Browser | HTML, CSS, JavaScript, WebGPU, single-file HTML export |
| .NET recreation (devclass.com, Nov 2024) | Desktop, cross-platform | Modern .NET, built “for fun” |
| WebVB Studio | Browser | VB6-style syntax plus Python, polished free IDE |
The differentiators, per the project’s own description, are the VB-style source runtime, the debugger, and the single-file HTML application exporter — pieces the .NET-based recreation did not offer. Where WebVB Studio blends VB6 syntax with Python, VB6 Studio Web commits to the classic VB6 model end to end.
So which matters more? They serve different goals: desktop nostalgia versus a shareable, zero-install web artifact. This project’s bet is on the browser.
Should Developers Take Browser-Native VB6 Seriously?
Yes — the project is a complete toolchain, not a demo, and its author frames it as a genuine RAD environment. Wiesław Šoltés’ announcement lists the full stack: “a browser-native IDE, VB-style source runtime, form designer, browser control library, debugger, and single-file HTML application exporter.” That is the entire build-run-debug-ship cycle in one package.
Skeptics may see Visual Basic 6 recreations as nostalgia. The counterargument comes from what the project actually demonstrates. The GeekNews coverage highlights a working Northwind Traders order entry example — the classic sample scenario — complete with form design tools. Screenshots show real project structure: a Project1.vbp with forms frmOrders.frm and Form1.frm, plus a modUtilities.bas module, and a Properties panel with precise control measurements. This is a functioning environment, not a mockup.
For different audiences, the value differs:
- Developers maintaining legacy VB6 knowledge get a modern, install-free playground.
- Educators can teach classic event-driven RAD without any installation.
- Hobbyists can build small utilities and export them as single HTML files.
- Historians of developer tooling get a faithful, inspectable recreation.
- Web developers can study how a full IDE fits into browser technologies.
The QWE AI Academy guide’s verdict is that this project offers “the classic shell feel plus a runtime, dozens of controls, a real debugger loop” — a combination it distinguishes from lighter-weight alternatives. The project is open on GitHub under wieslawsoltes/VB6, so anyone can evaluate it directly.
In my opinion, the most interesting part is the export story: classic RAD logic with a modern, zero-dependency delivery target. That combination is genuinely new.
Frequently Asked Questions
What is VB6 Studio Web?
VB6 Studio Web is a browser-native recreation of the classic Visual Basic 6 IDE, built by Wiesław Šoltés in HTML, CSS, and JavaScript. It includes a form designer, a VB-style source runtime, a controls library, a debugger, and a single-file HTML application exporter.
Can you build complete applications with it?
According to the project’s author, the toolchain covers the full RAD loop: designing forms, running VB-style source code in the browser, debugging, and exporting a finished app. The exported result is a single-file HTML application that runs standalone.
Does VB6 Studio Web require installation?
No installation is required, since the IDE runs natively in the browser using standard web technologies. The project is available on GitHub under wieslawsoltes/VB6, including the form designer, runtime, and debugger components.
How does it differ from other VB6 revival projects?
Earlier efforts, such as a cross-platform VB6-style IDE recreated in modern .NET covered by devclass.com in November 2024, focused on desktop tooling. VB6 Studio Web targets the browser directly and adds WebGPU drawing plus single-file HTML app export, which no .NET-based recreation offered.
Summary
VB6 Studio Web shows that a full classic IDE can live entirely in the browser. The key takeaways:
- Complete toolchain: IDE, form designer, VB-style source runtime, controls library, debugger, and exporter — all built in HTML, CSS, and JavaScript by Wiesław Šoltés.
- Zero-install RAD: the environment runs natively in the browser, removing the classic setup barrier for teaching, prototyping, and tinkering.
- Modern rendering: WebGPU drawing powers the visual IDE, supporting a faithful recreation of the classic shell and its design-time surfaces.
- A new deployment model: single-file HTML app export means finished applications ship as one standalone file — something the .NET-based VB6 recreation covered by devclass.com in November 2024 did not offer.
- Real, demonstrable output: coverage highlights a Northwind Traders order entry example, and the full project is open on GitHub at wieslawsoltes/VB6.
If classic Visual Basic 6 was part of your story, open the repository and try the form designer for yourself — then check how the debugger loop and export flow fit together in a single browser tab.