How to use inline styles in React.js

How to use inline styles in React.js

Inline styles in React.js offer a unique and powerful way to apply CSS directly within your JavaScript code. This approach, particularly in React, merges the styling and the component logic in a seamless manner, allowing developers to maintain style and functionality in close proximity.

Introduction to Inline Styling in React.js

In React.js, styling components can be achieved through various methods, with inline styling being one of the most straightforward. Inline styles in React involve writing CSS rules directly within the component’s JSX code. This method differs from traditional CSS styling as it involves passing a JavaScript object with style properties to the element’s style attribute. This approach is particularly useful for small-scale styling or when the style needs to be dynamically changed based on the component’s state or props.

Basics of Inline Styling

Applying inline styles in React is done by assigning a JavaScript object to the style attribute of a JSX element. Each key-value pair within this object represents a CSS property and its value. Unlike traditional CSS, in React’s inline styling, you need to use camelCase syntax for multi-word CSS properties.

Syntax of Inline Style Objects

The syntax for inline styles in React is a bit different from regular CSS. Instead of using kebab-case and strings, you use camelCase and values often represented as strings or numbers. For example, a CSS rule like font-size: 12px; would translate to { fontSize: 12 } in React’s inline style syntax.

Applying Styles to JSX Elements

To apply inline styles in JSX, you simply pass the style object to the style attribute of a JSX element. Here’s an example:

const divStyle = {
color: 'blue',
backgroundColor: 'lightgray',

function HelloWorldComponent() {
return <div style={divStyle}>Hello World!</div>;

Advantages and Disadvantages of Inline Styling

Using inline styles comes with its set of advantages and disadvantages. On the positive side, it allows for quick styling and easy dynamic changes based on component state or props. However, it can lead to code redundancy and difficulties in maintaining styles for large projects.

Writing Inline Styles

Converting traditional CSS to inline style objects in React can be straightforward but requires attention to syntax differences and nuances. Inline styles in React do not support pseudo-classes or media queries directly, so alternative approaches such as CSS-in-JS libraries might be needed for complex styling.

CamelCase vs. Kebab-case

In inline styles, React follows the JavaScript naming convention, which is camelCase. Therefore, CSS properties like background-color and font-size become backgroundColor and fontSize respectively in inline styles.

Numeric Values in Inline Styles

When using numerical values in inline styles, React assumes pixel units by default if no unit is specified. However, for other units (like em, vh, %), the value must be specified as a string, e.g., { width: '50%' }.

Dynamic Inline Styles

Dynamic inline styles in React are powerful for changing styles based on component state or props. For instance, you can change the style of an element based on user interaction or data fetched from an API.

Performance Considerations

While inline styles offer convenience and flexibility, they can also impact performance, especially in larger applications. Each inline style object is unique to an instance of a component, which can lead to more memory usage and slower rendering in some cases.

Organizing Styles for Larger Applications

The key to organizing inline styles for larger applications is consistency and modularity. It’s important to define styles in a way that they are easily maintainable and reusable. One best practice is to use JavaScript objects to encapsulate styles related to specific components or functionality. This not only enhances readability but also makes it easier to update styles as the application evolves.

Component-specific Styles vs. Shared Style Objects

While component-specific styles provide encapsulation and modularity, shared style objects promote reusability and uniformity across the application. The decision to use either approach should be based on the scope and reusability of the styles. If a style is unique to a single component, it’s best to define it within that component. However, for styles that are common across multiple components, such as theme colors or typography, shared style objects are more efficient.

Using JavaScript Objects for Styling

Defining styles as JavaScript objects allows you to leverage the full power of JavaScript to create dynamic styles. These objects can contain any CSS properties and their values, which React will apply as inline styles to the components.

Creating Style Objects Outside of Render Method

To keep the render method clean and improve performance, it’s advisable to define style objects outside of it. This prevents the creation of new objects on each render call, which can lead to unnecessary re-renders and degraded performance.

Sharing Style Objects Across Components

When you have styles that are common across different components, consider defining them in a separate file and importing them where needed. This approach not only reduces duplication but also centralizes style management, making it easier to update and maintain.

Common Pitfalls and How to Avoid Them

Overriding Styles with Inline Styles

Inline styles take precedence over styles defined in external stylesheets, which can be both a feature and a pitfall. To manage style precedence effectively, use inline styles sparingly and only when necessary to override styles that are not easily accessible otherwise.

Specificity Issues with Inline Styles

Inline styles can cause specificity issues, as they are more specific than class selectors. To combat this, ensure that the use of inline styles is justified and plan your CSS architecture to minimize conflicts.

Mixing Inline Styles with Other Styling Methods

Combining inline styles with external stylesheets or CSS-in-JS libraries can lead to a fragmented styling approach. Establish guidelines for when to use each method and stick to them to maintain consistency across the codebase.

Inline Styles with CSS-in-JS Libraries

CSS-in-JS libraries like Styled-components or Emotion offer a way to write CSS directly within JavaScript files, providing scope and theme support while maintaining the benefits of inline styles. Compare these libraries to see which aligns best with your project’s requirements.

Accessibility Considerations

Accessibility should never be an afterthought. When using inline styles, ensure that styles do not hinder the accessibility of the application, such as maintaining proper contrast ratios and supporting dynamic text resizing.

Examples and Best Practices

Provide real-world examples where inline styles were effectively used in large projects. Discuss how best practices were applied to ensure that the application remained scalable and maintainable.

Alternatives to Inline Styling

Explore other styling approaches like CSS, SASS, LESS, and CSS Modules that offer more traditional styling methodologies. These can provide better performance and maintainability in some cases.

Overview of CSS, Pre-processors, and CSS Modules

Delve into how CSS and its pre-processors can offer more power and flexibility over plain inline styles. CSS Modules, in particular, provide a way to write CSS that’s scoped to individual components, avoiding global scope issues.

Comparison with CSS-in-JS Solutions

Discuss the pros and cons of CSS-in-JS solutions versus traditional CSS approaches. Consider factors like runtime performance, developer experience, and integration with existing tooling.


Inline styles in React.js can be a powerful tool when used appropriately. However, as applications scale, it becomes important to consider other styling approaches to maintain code quality and performance.

Sharing is caring

Did you like what Mehul Mohan wrote? Thank them for their work by sharing it on social media.


No comments so far