
Oracle Forms & Webswing
Bring Oracle Forms to the browser with Webswing and HTML5. Keep existing application logic while planning the next step in your modernisation.
Webswing runs the Oracle Forms client on the server and delivers the interface through an HTML5 browser. End users do not need a local Java runtime. In most cases, you can retain the existing Forms code; review customisations and local integrations for your particular application.
Start with a representative business workflow. Confirm that users can complete it in their intended browsers, then decide which screens or functions would benefit from further modernisation.
The classic Forms model isn’t natively portable to the browser, doesn’t embed easily inside modern web apps, and isn’t touch-friendly. Applets are long gone; FSAL/JWS complicate rollout and updates, and it’s hard to add progressive features or test at scale. Many teams want a web experience without a risky migration, a way to modernise step-by-step while maintaining the business logic that works.
Teams want a web experience without a risky migration. A way to modernise step-by-step while maintaining the business logic that works.
Webswing executes Oracle Forms on the server and renders the UI as HTML5 in the browser.
End-users need only a standard browser. No client Java, no FSAL/JWS, no extensions. Despite running in the browser, you keep "desktop-like" comfort: printing, clipboard, secure file upload/download (including drag-and-drop), and reports opening as PDF in a new tab. Operations are enterprise-ready from day one: SSO, reverse proxy, clustering, auditing, metrics, cloud-friendly delivery.
When you're ready, you can refresh the look via CSS and Web Components or inject HTML content directly into the Forms window.

For hybrid scenarios, the JavaScript ⇄ Forms bridge lets you pass values and trigger events between web content and Forms (e.g., using dispatchCustomEvent/FBean or the JS link described in the deck).
That's how you can place APEX reports or other web pages alongside Forms and orchestrate a seamless flow.
For the setup steps and a practical pilot checklist, read our Oracle Forms to web modernisation blueprint.
The most popular pattern is Forms + APEX in a single browser tab. You can also embed React/Angular or plain HTML to enrich a legacy process, pass data both ways via the JS bridge, and progressively move the pieces that benefit most from the web while leaving core PL/SQL where it shines. As you go, you can render Forms controls as HTML Web Components and apply CSS for a fresher, accessible look.

Get even more insights from our articles dedicated to Oracle Forms and Webswing usage



Today Webswing supports Oracle Forms 11, 12.2.1.19 and 14.1.2 and runs with Java 8, 11, 17, 21 and 25. Because the UI runs in the browser sandbox, standard web security rules apply (CORS, CSP, cookies). That means limited access to local file systems, network drivers, registry, and external desktop apps, and WebUtil usage is therefore constrained. If you rely on deep OS integrations, let's discuss patterns that fit your use-case.