# Paraivew on M1 Chip

**URL:** https://discourse.paraview.org/t/paraivew-on-m1-chip/11534
**Category:** ParaView Support
**Created:** [February 28, 2023, 7:01pm UTC](https://discourse.paraview.org/t/paraivew-on-m1-chip/11534 "2023-02-28T19:01:39Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![ahandeep\_manna](https://discourse.paraview.org/user_avatar/discourse.paraview.org/ahandeep_manna/32/9994_2.png) [@ahandeep\_manna](https://discourse.paraview.org/u/ahandeep_manna)
#### Post date: [February 28, 2023, 7:01pm UTC](https://discourse.paraview.org/t/paraivew-on-m1-chip/11534/1 "2023-02-28T19:01:39Z")

</div>

Hi,  
I’m using Paraview 5.10.0 on my Mac Book pro with the M1 chip. This version seems to function , however erraticaly where regular interval it cannot open an files although the UI seems to run. Can anyone help me regarding this ?

P.S: Is there a version of paraview which has/ is being developed for better functioning on the M1/2 chips?

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [February 28, 2023, 7:50pm UTC](https://discourse.paraview.org/t/paraivew-on-m1-chip/11534/2 "2023-02-28T19:50:29Z")

</div>

ParaView 5.10 has macOS arm64 builds. Can you be more specific about what steps are involved to trigger the problem you’re seeing?

---

<div class="post-metadata">

### Author: ![wascott](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/w/8e8cbc/32.png) [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [February 28, 2023, 7:56pm UTC](https://discourse.paraview.org/t/paraivew-on-m1-chip/11534/3 "2023-02-28T19:56:26Z")

</div>

Welcome to the ParaView community ahandeep!

Ben and ahandeep, There were issues with older ParaView M1 (ARM) builds. ParaView 5.11.0 is working correctly on M1/ARM. You may want to download the latest, and then reply here with whatever issues you find.

Alternatively, the x86 builds (again, use 5.11.0) work well. There is some significant start up latency the first time as the Mac processes the binary, probably running it through rosetta.

Alan

---

<div class="post-metadata">

### Author: ![ahandeep\_manna](https://discourse.paraview.org/user_avatar/discourse.paraview.org/ahandeep_manna/32/9994_2.png) [@ahandeep\_manna](https://discourse.paraview.org/u/ahandeep_manna)
#### Post date: [March 16, 2023, 9:12am UTC](https://discourse.paraview.org/t/paraivew-on-m1-chip/11534/4 "2023-03-16T09:12:46Z")

</div>

Hi All,

Thank you for your replies. But the problem still persists.

 ![Screen Shot 2023-03-15 at 21.12.18](https://discourse.paraview.org/uploads/default/original/2X/3/3456f0619aaa4775ef7a76dc33d237131551f3e5.jpeg)  
 ![Screen Shot 2023-03-15 at 21.12.30](https://discourse.paraview.org/uploads/default/original/2X/0/02e4543bedc4bf65997ed54163cc0cc9542554b4.jpeg)  
 ![Screen Shot 2023-03-15 at 21.12.41](https://discourse.paraview.org/uploads/default/original/2X/e/eca40a89719aa6b0db9e43b9f97b2110c253fd86.jpeg)

I have uploaded a screen shot of the problem. Whenever i try to open a xdmf file it just doesn’t open it. I checked it for other file types like .vtu,.pvd as well and it shows the same problem.

best,  
Ahan

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [April 24, 2023, 1:43am UTC](https://discourse.paraview.org/t/paraivew-on-m1-chip/11534/5 "2023-04-24T01:43:28Z")

</div>

Can you share your XDMF file? It could be that the reader has assumptions that don’t hold for non-Intel architectures in some cases.