In this blog post we are going to look at the new styling and other new options available in OpenAPI and SwaggerUI Quarkus (v1.10.0 +).


Default style

The default style for Swagger UI has changed from the vanilla Swagger UI to a Quarkus branded page:


In this post we mostly focus on Swagger UI, but the styling options also apply to the GraphQL UI and the Health UI.


Swagger UI Themes are now available in configuration, with the default theme being ‘feeling blue’.

You can change the theme by setting the quarkus.swagger-ui.theme property, for example:



You can also go back to the original (vanilla) Swagger UI theme:



Theme options available:

  • feeling-blue (default)
  • original
  • flattop
  • material
  • monokai
  • muted
  • newspaper
  • outline

As part of the custom branding, you can supply your own logo to replace the Quarkus logo. For example, let say you own company that makes everything, ACME, and you are using REST Services for your online store, and wants to brand the Swagger UI Page:

NOTE: Hot reload is not working for logo changes, and remember browser cache, you might need to force refresh your browser.

acme logo

To supply your own logo, you need to place a file called logo.png in src/main/resources/META-INF/branding.


You can go further, and supply your own style.css, to fine-tune the branding. In example, to change the topbar of the Swagger-UI screen to the corporate colors of ACME:

    box-sizing: border-box;
    overflow: -moz-scrollbars-vertical;
    overflow-y: scroll;

    box-sizing: inherit;

    background: white;

.swagger-ui .topbar { <1>
    background-color: whitesmoke;

#footer {
    background-color: whitesmoke;
    text-align: center;

<1> here set the topbar background color.

acme css

You can change any styling element in this css file, you need to place this file called style.css in src/main/resources/META-INF/branding.

Other styling options

You can also set the HTML title, and add a footer:

quarkus.swagger-ui.title=ACME API
quarkus.swagger-ui.footer=&#169; 2020 . ACME

Along with other OpenAPI Header fields that can be set via config (as discussed in this post): online store API make everything, and sell it online IT 2.0

The UI is now fully branded:

acme footer

Other Swagger UI Options

Another new feature available in Quarkus (v1.10.0 +) is the ability to set any of the configuration options available in Swagger UI. As an example, we can set the urls and add the petstore (as the default selected option) to Swagger UI:


This will change the topbar to have a dropdown box with the urls provided:


Another example, supportedSubmitMethods can hide the Try it out button for certain HTTP Method Types:


Note below the missing Try it out button on the POST

try it out

All other Swagger UI options are now available to configure the UI.

Other Small new features

Two small new features in OpenAPI and Swagger UI, the ability to add the Health Endpoints and the ability to disable the UI and/or Schema in Runtime.

Add Health API to Open API

If you are using the smallrye-health extension, you can add the Health Endpoints to OpenAPI:


Disable in Runtime

If you included the UI in your app (quarkus.swagger-ui.always-include=true), you can now disable it when starting the application.

java -jar -Dquarkus.swagger-ui.enable=false target/yourapp-1.0.0-runner.jar

This will return a HTTP 404 (Not Found) on the Swagger UI page.

Similarly you can disable the schema (usually under /openapi) by doing:

java -jar -Dquarkus.smallrye-openapi.enable=false target/yourapp-1.0.0-runner.jar