colorbar — Show, hide, or toggle colorbars in MATLAB and RunMat plotting.
colorbar controls the color scale associated with the current or specified axes. Each enabled colorbar has a registered graphics identity and an independent lifetime. Default RunMat behavior preserves the historical toggle and logical result; MATLAB compatibility mode enables and returns a ColorBar handle.
Syntax
c = colorbar(ax, mode)
c = colorbar()
enabled = colorbar()
enabled = colorbar(mode)Inputs
ax- Type
AxesHandle- Required
- Yes
- Description
- Associated axes, without changing current selection.
mode- Type
StringScalar- Required
- No
- Description
- Colorbar mode token ('on'|'off').
Returns
c- Type
Any- Description
- Registered ColorBar identity in MATLAB profile, or logical state in RunMat profile.
enabled- Type
LogicalArray- Description
- Colorbar enabled state after command execution.
Errors
RunMat:colorbar:InvalidArgument- When
- Colorbar mode argument is unsupported.
- Message
colorbar: invalid argument
RunMat:colorbar:TooManyOutputs- When
- More than one output is requested, or off requests an output in MATLAB profile.
- Message
colorbar: at most one output is supported
Behavior
colorbar on enables the colorbar for the current axes.
colorbar off disables the colorbar for the current axes.
With no mode, RunMat toggles and returns logical enabled state. MATLAB compatibility mode enables an existing or new colorbar and returns its registered handle; repeated calls reuse that handle.
Colorbar visibility is subplot-local and does not automatically affect other axes.
An optional leading axes handle targets that axes without changing selection. off deletes the associated ColorBar identity. Setting a ColorBar handle's Visible property to false hides the live object without deleting its identity.
ColorBar handles expose Type, Parent, Children, and Visible. Position, Location, Labels, and colorbar-specific label children are not yet supported. MATLAB-profile off calls have no output.
Placement and display
These commands update shared graphics state and may notify figure observers. Numeric array acceleration remains with the original plotting/rendering pipeline; the commands do not launch array-provider kernels. Graphics display requires a browser graphics host or a desktop graphics host.
Control arguments must already be host values. Unsupported resident controls reject without provider downloads; existing resident plot buffers stay owned by their plotting/rendering paths. Invalid syntax and excess output requests are checked before creating or changing graphics state.
Examples
Show a colorbar for a scaled image
[X, Y] = meshgrid(linspace(-3, 3, 60), linspace(-3, 3, 60));
A = sin(X) .* cos(Y);
imagesc(A);
colorbar on;Use colorbars independently across subplots
[X,Y] = meshgrid(linspace(-3,3,40)); Z = sin(X).*cos(Y);
ax1 = subplot(1,2,1); contourf(X,Y,Z); colorbar on;
ax2 = subplot(1,2,2); surf(X,Y,Z); colorbar off;Using colorbar with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how colorbar changes the result.
Run a small colorbar example, explain the result, then change one input and compare the output.
FAQ
How do I add a label to the colorbar?⌄
ColorBar-specific label children and ylabel(colorbarHandle,...) are not yet supported. You can annotate the axes with ylabel('Intensity'), but that labels the axes, not the colorbar. For example, imagesc(peaks(50)); colorbar on; ylabel('Intensity'); adds an axes label alongside the scale.
Can I limit the colorbar range without clipping the data?⌄
Set caxis([cmin cmax]) (or clim([cmin cmax])) on the axes to control the color mapping range. Values outside that range get clamped to the endpoint colors, but the underlying data stays intact.
Does the colorbar track across subplots automatically?⌄
No. Colorbar state is subplot-local, so each axes manages its own colorbar independently. You need to call colorbar on in each subplot where you want one visible.
Related Plotting functions
2D Charts
area · bar · errorbar · heatmap · hist · histogram · loglog · pie · plot · scatter · semilogx · semilogy · stairs · stem
Other
addpoints · ancestor · animatedline · autumn · axes · barh · bone · caxis · cla · clf · clim · colorcube · colororder · cool · copper · copyobj · cylinder · daspect · datacursormode · dataTipTextRow · drawnow · fcontour · figure · fill · fill3 · findobj · fsurf · gobjects · gray · groot · hgload · hgsave · hidden · histogram2 · hold · hot · inferno · isgraphics · ishandle · jet · line · lines · linkaxes · magma · openfig · opengl · pan · parula · patch · pink · plasma · plotmatrix · plotyy · polarhistogram · polarplot · polarscatter · print · quiver3 · ribbon · saveas · savefig · sphere · spring · stackedplot · subtitle · summer · suptitle · text · textscatter · textscatter3 · triplot · turbo · viridis · waitbar · winter · wordcloud · xlabel · xlim · xline · xscale · xtickangle · xtickformat · xticklabels · xticks · ylabel · ylim · yline · yscale · ytickangle · ytickformat · yticklabels · yticks · zlim · zoom
More plotting resources
About RunMat
RunMat is a runtime that executes MATLAB-syntax code fast on any GPU. The runtime is free for individuals, including freelancers; students and faculty at an academic institution, for teaching or research there; contributors to an open-source project, for work on that project; organizations with 250 or fewer people and US$10M or less in annual revenue; and anyone, for non-production use. See runmat.com/license.
- RunMat automatically optimizes your math for GPU execution on Apple, Nvidia, and AMD hardware. No code changes needed. Simulations that took hours now take minutes.
- Start running code in seconds. RunMat runs in the browser, on the desktop, or from the CLI. No license server, no IT ticket.