Ribbon UI Studio

Official documentation · v4.0.0

From an Office file to RibbonX, VBA and a distributable add-in.

A practical guide to editing customUI XML, working with VBA modules, checking callbacks, using imageMso, creating Excel, Word and PowerPoint add-ins, and packaging them for Windows.

RibbonX XMLVBAExcelWordPowerPointWindows
Ribbon UI Studio v4ExcelWordPowerPointOffice Open XMLInstallerLab deployment

Ribbon UI Studio v4.0.0

What's new in v4 and edition guide

v4 expands Ribbon UI Studio with three visual areas: Ribbon design, native VBA UserForms and Modern Forms. The two form systems are different and should not be confused.

🎛️ Ribbon Visual Designer

Structural designer with live preview, tree, toolbox, properties, imageMso, visible/enabled state and before/after placement. Apply to file writes the resulting RibbonX XML back to the Office file.

🧩 VBA UserForm Designer · Community + PRO

Works with native MSForms/VBA UserForms. It can create or edit classic forms while preserving existing event code and resources where supported.

✨ Modern Forms · PRO

Separate JSON-based system with its own runtime. Includes TextBox, ComboBox, CheckBox, Date, Calendar, File/Folder, Label, Image and Button plus themes, scale and elevation.

💬 Modern MsgBox · PRO

OER_ModernMsgBox keeps a VBA-friendly workflow for common button groups and results, with native MsgBox fallback when the modern runtime cannot be used.

🔐 Add-in Licensing · PRO

PRO can add licensing protection to an Office add-in and remove it again when it is no longer required. Ribbon UI Studio's own license and the license embedded in an add-in are separate.

📦 InstallerLab deployment

Final Bundle Installer generation requires InstallerLab to be installed. Ribbon UI Studio prepares the add-in and deployment project; InstallerLab generates the Bundle Installer.

InstallerLab ↗

Community vs PRO

CapabilityCommunityPRO
RibbonX / VBA editing✓✓
Ribbon Visual Designer✓✓
Classic native VBA UserForms✓✓
imageMso / callbacks / diagnostics✓✓
Modern Forms Designer + runtime—✓
Modern VBA-compatible dialogs—✓
Add / remove add-in licensing—✓
Advanced packaging with InstallerLab—✓

InstallerLab is a separate application and must be installed to generate the Bundle Installer. installerlab.website ↗

About the LittleAPI screenshots

LittleAPI is shown as a real-world add-in built with Ribbon UI Studio capabilities. It does not mean LittleAPI is a required built-in feature of the editor.

3main Office hosts
2RibbonX schemas
1XML + VBA + distribution workflow
Overview

What Ribbon UI Studio is designed to solve

Ribbon UI Studio is a Windows desktop application focused on Microsoft Office RibbonX customization. Instead of splitting XML, callbacks, VBA modules, icons and packaging across unrelated tools, it keeps them around the same Office document or add-in.

Office file editor

Open the Office Open XML package and work with customUI/customUI14, images and related content without manually editing the ZIP.

End-to-end workflow

Design the ribbon, check callbacks, edit VBA, create an add-in and prepare its Windows installer from the same product.

! Always keep a backup before modifying an existing Office document.
Quick start

Your first customization in six steps

01
Open an Office fileChoose a compatible document or add-in and let the project tree expose its contents.
02
Create or open customUIChoose Office 2007 or Office 2010+ depending on the schema you need.
03
Edit XMLWork in Monaco with tabs, formatting and RibbonX templates.
04
Validate and previewCheck syntax, IDs, callbacks and images before opening Office.
05
Connect VBAGenerate missing callbacks and edit document modules when appropriate.
06
Save and testWrite changes back to the Office file and test the ribbon in the host application.
Office format

Office 2007 and Office 2010+ use different RibbonX parts

Ribbon UI Studio recognizes both common Open XML package locations and can create the correct part when it does not exist yet.

SchemaPathNamespace
Office 2007customUI/customUI.xml2006/01/customui
Office 2010+customUI/customUI14.xml2009/07/customui

For VBA callbacks, a macro-free file such as .xlsx, .docx or .pptx must first be saved to a macro-enabled format such as .xlsm, .docm or .pptm.

Monaco + RibbonX

Edit XML as code, not as a black box

The editor keeps documents separated and lets you switch between RibbonX XML and VBA modules without mixing their save targets. Built-in templates provide starting points for common ribbons, dynamic menus, galleries and Office-specific workflows.

customUI14.xml
<customUI xmlns="http://schemas.microsoft.com/office/2009/07/customui">
  <ribbon>
    <tabs>
      <tab id="tabTools" label="My Tools">
        <group id="grpMain" label="Actions">
          <button id="btnRun"
                  label="Run"
                  imageMso="HappyFace"
                  size="large"
                  onAction="RunAction" />
        </group>
      </tab>
    </tabs>
  </ribbon>
</customUI>
Use stable custom IDs and avoid duplicates across controls in the same Ribbon.
Review before Office

Visual preview and diagnostics

Ribbon UI Studio can build a ribbon representation without launching Office. The preview interprets tabs, groups, controls, imageMso, embedded images and callback presence so problems can be spotted before final testing.

XML

Checks valid XML and the expected namespace.

IDs

Helps detect duplicated or inconsistent identifiers.

Callbacks

Cross-checks callback attributes against available VBA code.

VBA

Callbacks no longer have to be copied manually

When the file supports macros, Ribbon UI Studio can read VBA modules, open them as editor documents and save back to the correct module. It can also create missing callback signatures from RibbonX attributes.

RibbonCallbacks.bas
Public Sub RunAction(control As IRibbonControl)
    MsgBox "Ribbon action executed", vbInformation
End Sub
VBA project automation depends on access to the VBA object model. If Office blocks it, module editing or generation cannot complete.
imageMso

Built-in icons and custom resources

The imageMso gallery uses Office identifiers to help locate and copy the correct name. You can also work with custom images embedded in the Office package and verify that the preview can resolve them.

imageMso+PNG custom→Ribbon XML→Preview
Creation

Create Excel, Word and PowerPoint add-ins

The creation workflow can prepare the add-in file, a starter ribbon and the RibbonCallbacks module so the project starts from a coherent structure.

HostAdd-inTypical use
Excel.xlamExcel tools and automation
Word.dotmDocument templates and tools
PowerPoint.ppamPresentation tools
Distribution

Package Office add-ins for Windows

The stable v4.0.0 packaging workflow uses InstallerLab to compile the Windows installer for .xlam, .dotm and .ppam add-ins.

IL
InstallerLab

When protection or obfuscation is enabled, the workflow works on a temporary copy so the original add-in is not modified.

installerlab.website ↗

Comparison

How it compares with existing tools

These tools do not all target the same problem. Office RibbonX Editor is a strong focused editor; Visual Studio/VSTO is a full development environment; the original Custom UI Editor is a legacy reference. Ribbon UI Studio aims to cover XML + VBA + add-in + distribution in one application.

CapabilityRibbon UI StudioOffice RibbonX EditorOffice Custom UI EditorVisual Studio / VSTO
Primary focusRibbonX + VBA + add-in workflowFocused RibbonX editingClassic Custom UI editing.NET Office solution development
Standalone appYesYesYesNo, requires Visual Studio
Office 2007 / 2010+ customUIYesYesYesYes, via Ribbon XML
Multi-tab editingYesYesClassic workflowIDE tabs
XML validationYesYesYesIDE/XML tooling
Generate callback signaturesYesYesYesProject code
Edit VBA modules inside the fileIntegratedNot its primary workflowNot its primary workflowVSTO primarily uses C#/VB.NET
Host-aware ribbon previewIntegratedXML/icon focusedClassic XML editorVisual Designer available with limitations
imageMso / custom imagesYesYesYesYes
Create .xlam / .dotm / .ppamIntegratedPrimarily edits existing filesPrimarily edits existing filesDifferent add-in/project model
Build Windows installerIntegrated with InstallerLab——Handled with deployment tooling
Best fit when…You want RibbonX, VBA and distribution togetherYou want a mature focused RibbonX editorYou maintain a legacy workflowYou are building a full .NET Office solution
This is a scope comparison, not a quality ranking. Each option can be the right choice for a different project.
Common issues

Before assuming the ribbon is broken

Callback does not run

Check the exact XML name, confirm the file supports macros and ensure the procedure exists in an accessible standard module.

Office does not show the ribbon

Validate XML, check the namespace and confirm customUI.xml/customUI14.xml is correctly registered in the package.

VBA cannot be edited

Office can block programmatic access to the VBA project. Review Trust Center settings and use trusted documents.

Image does not appear

Distinguish imageMso from custom images. Custom images need the correct relationship and resource inside the Office package.