Go to wurkr.io and click “Sign up”. Fill out the details and you are good to go.

Co-Working, Team Meeting, Quick catchups, All Hands in, Daily Stand Ups, Virtual HQ, Kick-Offs, Client Meetings, Coffee Chat, One to One, Feedback Session, Happy Hour, Team Building, Office Hours, Ice Breakers, Onboarding New Team Members, Game Night, Brainstorming, Sprints, Workshop, Interviews, Project Room, Retrospective, Networking Event, Virtual Event, Conference, Strategic Review, Training, Paired Programming, Multi Room Interviewing

Book a chat with one of our workplace specialist links here 

Each workspace has between 11-23 rooms, but you can create unlimited workspaces giving you the ability to scale your team from 0-1000s.

To invite a guest:

You can simply click Add – Guest – enable guest invite link and click copy – include this calendar invite, email etc. Anyone who has the link can join the room.

Invite a member and offer them full access:

By clicking on “Add – Invite New Member – Invite team link – copying this and sending it to anyone you want to invite as a team member.” Following this step will give the invited member full access.

We recommend no more than 200 users in each workspace. 

You can fit from 1 -50  in each room, though there is no set limit.

The pay will come into effect once your trial period is over. You can select one of the various paid packages we offer. 

Once your free trial period is over, your package will be downgraded to Lite Package and you will be contacted for a paid package.

All the plans start with a free trial to help you understand Wurkr better.

You can extend your free trial by dropping a Wurkr Review on the G2 Website. You can also send us a written or video testimonial to avail an extended free trial period.

Wurkr is priced on the basis of Per User Per Month. 

Yes, we accept most of the currencies.

We accept payments through DD and Credit card. 

No, you don’t need to provide credit card details while you sign up. 

Yes, we provide the payment receipt in the PDF file format through email.

Yes, you can contact our support team for the same. 

This can be provided to you upon request. 

Yes, the billing frequency can  be monthly, quarterly or annual as per your requirements. We offer flexible billing. 

Yes, you can cancel the subscription with 30 days prior notice. 

Please reach out to us via our Partners page for more information.

Please reach out to us via our Support page for more information.

Operation system Browsers Receiving streams Sending streams
  • Chrome
  • Firefox
  • Safari
  • Edge
Supported Supported
  • Chrome
  • Firefox
  • Edge
Supported Supported
  • Chrome
Supported Supported


  • On all AMD-based and some Intel-based devices with the Windows operating system, if Chrome uses the H.264 codec, the video transmission bitrate may be lower than the set value. To resolve this issue, you can set the browser to use the VP8 codec or try to disable hardware acceleration.
  • Chrome 84 on macOS has a known issue: When using the H.264 codec, WebRTC can experience a sudden drop in the frame rate. For details, see the official Google bug reports: Issue 1088650 and Issue 12704. Agora recommends using VP8 instead of H.264 for Chrome 84 and later versions on macOS.


  • When the Web SDK on Firefox communicates with the SDK on some devices, the video on Firefox is rotated.
  • Firefox does not support changing the frame rate (30 fps by default).
  • Firefox does not support setting the audio encoding rate.
  • Setting the video profile on Firefox does not take effect on the following devices:
    • MacBook Pro (13-inch, 2016, Two Thunderbolt 3 ports)
    • Windows 10 (MI)
  • On Macs with the Apple M1 chip, Firefox does not support H.264. For details, see the Firefox documentation.
  • Firefox dose not support getting CodecTypesendFrameRate and captureFrameRate.

Other restrictions

  • On Chrome 81 or later, Safari, and Firefox, device IDs are only available after the user has granted permission to use the media device. See Why can’t I get device ID on Chrome 81? This restriction affects the getMicrophonesgetCameras, and getPlaybackDevices methods.

  • The setPlaybackDevice method is only supported on Chrome. Calling this method on other browsers throws the NOT_SUPPORTED error.

  • The setOptimizationMode method and the optimizationMode parameter in CameraVideoTrackInitConfigScreenVideoTrackInitConfig, and CustomVideoTrackInitConfig are only supported on Chrome.

  • Calling createScreenVideoTrack to enable screen sharing has the following restrictions:

    • The Web SDK supports screen sharing on Chrome 58 or later. If the Chrome version is earlier than 72, you need to add the Google Chrome Extension for Screen Sharing provided by Agora, get the extensionId, and set the extensionId parameter when you create a video track for screen sharing. If the Chrome version is 72 or later, simply call createScreenVideoTrack.
    • The Web SDK supports screen sharing on Firefox 56 or later. Firefox on Windows does not support the application mode.
    • The Web SDK supports screen sharing on Edge 80 or later on Windows 10+.
    • The Web SDK supports screen sharing on macOS Safari 13 or later. The end-user can only share the whole screen on Safari.
    • The Web SDK supports sharing the local audio playback when sharing a screen on Chrome 74 or later. To share the audio, set the withAudio parameter when calling createScreenVideoTrack. On Windows, this function allows you to share the audio when sharing the entire screen and sharing Chrome tabs, but not when sharing the application window. On macOS, this function allows you to share the audio only when sharing Chrome tabs.
  • The setBeautyEffect method is only supported on the following browsers and versions:

    • Chrome 65 or later.
    • Safari 12 or later.
    • Firefox 70.0.1 or later.