Visualforce support matrix
Inspect the running local renderer's support rows and its preview boundary. The endpoint reports the binary you started, so it stays bound to that local implementation.
Use this page when checking the local Visualforce preview boundary. The support map carries the current local contract and hosted gaps.
v0.3.0 supports Visualforce API 59.0-68.0. Preserved historical page versions outside that window are unsupported.
Start here
Start with controller logic, page routes, standard components, static resources, uploads, remoting, and AJAX refresh paths. Then check the detailed source for current limits.
Glade serves Visualforce previews for local development. It does not promise Salesforce chrome, exact lifecycle timing, or byte-for-byte PDF output. Use Salesforce for hosted rendering proof.
Inspect the running implementation
Visualforce local rendering is a preview feature. It gives useful local /apex/<PageName> previews, not full hosted Visualforce parity.
Start the Visualforce dev server from a Salesforce-shaped project:
glade dev vf --project . --addr 127.0.0.1:8080Startup output lists the local page routes and watched source families:
Visualforce dev server: http://127.0.0.1:8080
Pages:
/apex/Core
/apex/CardHost
Watching ... for .page, .component, .cls, aura, lwc, and static resource changes.Open the listed /apex/<PageName> route in a browser. Render diagnostics use a local HTML overlay with the page file and Visualforce expression when Glade can pin the source. The same server exposes the current standard-component support rows as local JSON:
curl http://127.0.0.1:8080/services/data/v65.0/glade/visualforce/supportUse --port 8080 for the common localhost shortcut. Use an ephemeral address and a ready file for scripts:
glade dev vf --project . --addr 127.0.0.1:0 --ready-file /tmp/glade-vf-ready.jsonThe local renderer covers common standard components, custom components, controller actions, page messages, expression and form binding, static resources, uploads, remoting envelopes, Lightning Out/LWC hosts, AJAX refresh paths, and local PDF fallback output. It does not promise Salesforce-hosted chrome, every component edge, exact lifecycle timing, Apex PageReference.getContent* parity, or byte-for-byte PDF output.
Form posts carry signed Visualforce view state and a CSRF token. Controller and extension state comes back across posts, while Apex fields marked transient stay out of the saved state. Lightning Out pages validate ltng:outApp dependencies before creating local LWC modules, so a missing Aura dependency or component name reports a local rendering diagnostic instead of a browser fetch failure.
The local support JSON is an implementation inventory. It is not a Salesforce rendering comparison. Record the binary version and the tested page when reporting a mismatch.