Accepted answer

You should prefer your second example, to pass the props individually. There you can see explicitly which arguments are passed and can quickly compare with which arguments are expected. This makes collaboration along people much easier and makes the state of the application more clear.

I personally try to avoid passing whole objects if it's not needed. It's like the spread operator where there can be any property inside and it is much harder to debug in a bigger scope.

Some additions to pure react like prop-types or typescript might help to define clear and expected properties in a big application


You can pass props into JSX element as single object using React.createElement function.

Because each JSX element is just syntactic sugar for calling React.createElement.

The following 2 lines are equal for React:

<Button variant={"secondary"}>Add</Button>
{React.createElement(Button, {variant: "secondary", children: "Add"})}


It depends on that Object. Do you need ALL of its properties to be passed to another component? Or... You might need to pass 2 properties out of 5 to a specific component?

  • If you don't need to pass ALL of its properties, I recommend passing the Properties as Props
  • BUT, if you are 100% sure that you NEED ALL THE PROPERTIES to be passed together, I recommend passing the whole Object as Props in that case as it would be much clearer code and keeps you away from forgotten to pass something. For example; When you add a new property to that object, you don't have to pass it, as you are already passing the whole Object!

Well, if you aren't certain about your current/future purpose of that Object as you might need to EXCLUDE some properties soon, you probably should pass its properties individually in that case, instead of passing some non-used properties to the other component.


I agree with the other answers that in short, it depends, and the points raised in other answers are all valid.

Some other points I would like to add that also leans towards using individual properties are as follows -

  • Sometimes its not even the question of whether Do I need all the properties? It should be more of the question - Do I want to restrict the usage of the component to when I only have the complete object and not just a subset of properties.

Take for example a widget to display a car's image, make and model as part of a list of a widgets, its not reasonable to expect the full Car type to be available in order to display only the car's image, make and model. Only those 3 properties are required.

  • With the likes of rise of the likes of graphql where we can restrict the properties of data being returned about a type, we shouldn't always assume that components will have access to fully populated objects based on a type.

  • Lastly on the point of causing unnecessary rerenders of components down the tree, always passing the full object around, you are likely to cause all children that consumes that object will rerender when the object is updated. However passing separate properties to children, usually primitives, we can better mitigate against unnecessary rerenders


The whole point of objects is to encapsulate similar properties together. If you have about 10 properties and want to use them in your child component, stick with objects.

But in your case, my opinion is to use your second example as it makes the code in the child component simpler.

To the best of both worlds simply destructure those props that you need inside your child component.

Like this:

function InnerComponent({ name, image }) {

If you don't like braces in the arguments do this:

function InnerComponent(props) {
  const { name, image } = props;


Passing multiple props to a child component is the preferred way of passing props to child components. This will help you in tracking the state of the application in the child component. Also, feel free to use the prop-types module. It acts like generics in Java and provides type safety for the props to pass in.


If you aren't making use of all the properties within the object, its better to pass the required properties separately as it can help in performance optimisation when the Child component is a PureComponent of use shouldComponentUpdate. In such a case, only when the props used by the Child component change, its will re-render and not when an unused property from within the object has changed.

However if your are making use of all the properties within the object, it doesn't make much of a difference event if you pass down the object as a props, provided you handle the mutations of the object correctly.


Since JavaScript has no type annotation, the second choice would be much preferable, as mentioned by @mstruebing the code will be more maintainable. However, if you are using TypeScript React (which support type annotation), both choice would be equally clear. But do keep in mind, the first choice promotes tight coupling between views and models, this allows fast development as you don't have to type much; while the second choice might slows down development but you have higher flexibility and tolerance to future changes.

So, the gauge is: if you favor development speed over flexibility, go for choice 1; if you favor flexibility over development speed, go for choice 2.

Extra notes

Ok, when should we favor development speed over flexibility? Here's my 2 cents.

If your project was meant for short-term usage (for example developing an app just for collecting votes during election), then go for the first choice.

If your project was meant for long-term usage (for example online bank transaction portal), you should go for the second choice.


According to the principle of least privilege, this is a correct way:

<InnerComponent name={} image={object.image} />

This restricts InnerComponent from accidentally modifying original object or accessing properties that aren't intended for it.

Alternatively, properties could be picked from original object and passed as props:

<InnerComponent {...pick(object, 'name', 'image')} />

If there are numerous properties that are tedious to list, there may be single prop that accepts an object:

<InnerComponent object={pick(object, 'name', 'image')} />

Related Query

More Query from same tag